...

There is a new JSR-170 implementation of CHS forming in branch SAK-10366, this will use a more DAV compliant approach with the intention that it will be compatable with commercial JSR-170 implementations. The inforamtion below should now be considered informative on the subject, but it is not the way in which JSR-170 is being implemented. For more information on the current status please see http://bugs.sakaiproject.org/jira/browse/SAK-10366

...

Information below this point is deprecated

JSR-170 Implementation of ContentHostingService.

During the Summer of 2006, I did a JSR-170 Implementation of ContentHostingService as a prototype against the then Trunk 2.2 ContentHostingService. The implementation took the ContentHostingService API and re-implemented it using JSR-170 under the covers. It was done in in such a way as to allow JSR-170 clients (eg WebDAV implementations) to use the JSR-170 API directly and still obey the Sakai AuthZ implementation.

...

The terms JSR-170 and JCR are interchangeable

Structure

The ContentHostingService sits on-top of a JCRAdapter that connects it to the JCR implementation. The Content Entities have JCR implementations that are delivered from the JCRAdapter. Specialization to Jackrabbit is performed in the org.sakaiproject.content.jcr.jackrabbit package, which deals with the JAAS based integration between the JCR and Sakai and the configuration of the types within the JCR.

...