Hi,
What do you mean by extending Jackrabbit ? Maybe the Jackrabbit OCM contrib (in subfolder contrib/jcr-mapping) can be a great help. Using it, you can persist any kind of java objects into a JCR repository like Jackrabbit. It can add more abstraction on the JCR API from your business logic. Last info, if you plan to build your own CMS, you should take a look at the upcoming framework Sling. (http://wiki.apache.org/jackrabbit/ApacheSling). br, Christophe On 9/5/07, Reza Ghaffaripour <[EMAIL PROTECTED]> wrote: > > Hi, > > I am new to the concept of CMS and Jackrabbit. I was planning to create > an open source and specialized CMS for my offline media. I also decided > to be as much as possible in-dependent of the JSR and jackrabbit > interfaces and classes because they are almost new and change a lot. I > just wanted to know the best practices of using JSR/ Jackrabbit? Should > I extend Jackrabbit or just use it with some proxies/ associations? What > should be the degree of dependency to the JSR 170? > > Thanks > >
