I don't hate it (jackrabbit)Read that conclusion! I see a ray of hope."Perhaps the bisgget benefit of the JCR API is that it doesn't try to persist Java objects, and cares little about an application's object model. Instead, the JCR API focuses entirely on the content, or data, of an application. While this may at first sound like a step backwards, it actually creates a very clean and easy-to-use programming model with a sharp focus on a handful of data management tasks, such as versioning."A step backwards? Not at all - a huge step back in the right direction is more like it.I've always liked transactional API's, this is a transactional API. It might use the funky data model as I've termed it - but for content like this, it is likely acceptable.