Versions Compared

Old Version 32

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

There is currently a beta quality JCR implementation of Content Hosting in trunk. This work was originaly done and documented in SAK-10366. This is some good historical information available too, but that is now deprecated. This page will deal specifically with JCR information related to the ContentHostingService and parts of the Resources tool. For general information about JSR-170 support in Sakai see here

The very first phase of JCR integration for Resources is an implementation of the existing ContentHostingService API using a JCR backend. With this initial support, the Resources Tool and Sakai DAV are meant to operate as they stand with no changes to their code.

Installing the JCR ContentHostingService

Note

On the road to multiple CHS implementations, some properties which previously referred to the org.sakaiproject.content.api.ContentHostingService bean name itself must now refer to the specific implementation. This requires changes if you are using an existing sakai.properties. If you see errors during startup indicating things like 'prioritySortEnabled' not being settable, this is a likely cause.

Your sakai.properties should now look like:

No Format

# set to true to enable the release/retract and hiding of resources in ContentHostingService
availabilityChecksEnabled@org.sakaiproject.content.api.ContentHostingService.dbservice = true

# set to true to enable custom sorts within folders in ContentHostingService and the Resources tool
prioritySortEnabled@org.sakaiproject.content.api.ContentHostingService.dbservice = true

Sakai Trunk

Content Hosting service on jcr is available in trunk, and can be built as part of the framework profile. Deploy the famework with

...