...
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:
|
Sakai Trunk
Note: Some work on this is currently occuring in content branch SAK-12105. Should be merged back within a few weeks. SG - Nov 13, 2007
...
...
Content Hosting service on jcr is available in trunk, and can be built as part of the framework profile. Deploy the famework with
No Format |
---|
mvn -Pframework clean install sakai:deploy -Dmaven.tomcat.home=/tomcathome;
rm -rf /tomcathome/components/sakai-content-pack;
cd content;
mvn -Pframework-jcr clean install sakai:deploy -Dmaven.tomcat.home=/tomcathome
IEB - Dec 7, 2007 |
In addition, you can use the full-jcr maven profile to install everything with JCR including the content-providers, etc.
- If Sakai is already built and deployed, remove the following directory from the tomcat deploy
tomcat/components/sakai-content-pack - Then checkout and build the content branch
No Format svn co https://source.sakaiproject.org/svn/content/branches/SAK-12105 mvn clean install sakai:deploy -f SAK-12105/pom.xml -PJCR
- At the moment there is an issue with the content provider component. After installing remove components/sakai-content-providers-pack.
...