Hi Tony, On 06.05.2010 21:25, Tony Giaccone wrote: > > > I'm trying to understand the differences between sling and jackrabbit. I > understand that Jackrabbit is the underlying content repository that sling > uses.
Yes, Sling is a (Web) Application Framework for Java Content Repositories (JCR). Jackrabbit is an implementation of the Java Content Repository API specification. As such, Sling uses Jackrabbit as its repository for storage. > > As I read through the jackrabbit wiki, it seems clear that there's a database > behind jackrabbit, that holds information about the documents that are being > stored in the repository. Well, since Jackrabbit stores data, it must store the data somewhere. To this avail Jackrabbit uses persistence managers. There exist various persistence managers, most actually store the data in a database, actually only one or two tables in such a database. > > However, as I read through the sling docs, there's not much that discusses > the need for this database, is the because the sling distribution assumes > there is a jackrabbit server installed somewhere and that part of the > configuration of sling is to connect it to a JSR 170 Repository? Sling just writes to the repository using the JCR API and does not care, what actual backend storage is used. Out of the box, Sling comes with an embedded Jackrabbit repository which happens to use Derby as its persistence database. But since this is an implementation (or even an administrative) detail of Jackrabbit, Sling does not care, does not know and does not document this. Sling just cares for a proper implementation of the JCR API available. Hope this helps. Regards Felix > > Or is sling using some other kind of persistent store to hold document > information? > > > > Tony
