Confluence Docs 3.0 : Confluence Architecture This page last changed on Dec 17, 2007 by jnolen.
### Introduction These pages are internal developer documentation for Confluence. The main audience for these documents is Atlassian developers, but hopefully plugin and extension developers might benefit from knowing more about how the application works. There are, however, a few caveats: This documentation is incomplete. All system documentation is a work in progress, and more documents will come online as they are written. (This is, after all, a wiki.) Confluence has been in development since 2003, much longer than these documents have existed. There are many parts of the application that do not follow these guidelines, and some of the architecture documents represent how things should be from now on rather than how they were in the past ### Understanding Confluence These documents should give you some understanding of how the Confluence code-base is structured, where to find things, and where to put new things. High Level Architecture Overview Confluence Permissions Architecture |
### Developer Guidelines These documents are more general descriptions of How We Do Things Around Here. It's a good idea to be familiar with these documents, but keep in mind that no rule is set in stone, and the existence of a guideline does not absolve you from your responsibility to think. Spring Usage Guidelines Exception Handling Guidelines Logging Guidelines Deprecation Guidelines Hibernate Sessions and Transaction Management Guidelines Javadoc Standards Attachments: Confluence Layers.png (image/png)

Document generated by Confluence on Nov 05, 2009 23:34