THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Jackrabbit Branch Development / Integration
In this section I want to summarize the process of the content repository integration.
...
- When we have an external content Repository it's easy to connect third party tools to the repository (i.e. CMS Systems)
- If we have a generic JCR implementation we can simply add different content repositories
- Content Repositories allow easier maintenance of complex content structures, as contents are no longer stored in different tables (Content, Resource, ElectronicText ...).
- Content Repositories can provide revisioning of contents and content modifications
What has been done
- Created a new independent JCR module in the framework
- Start the Jackrabbit Container on ofbiz startup
- Created a Repository Factory
- Created a Jackrabbit - Ofbiz architecture proposal: OfbizJcrClassDiagram_17_04_2011.gif
- (Implementation of the proposal is done and will be committed after review)
Still to be done
Ideas
Table of Content
- Initial integration of the Jackrabbit repository - features and architecture description
- Design documents
- Configuration document
- Requirements and Ideas
- Current DB based content implementation vs JCR based content implementation
- Propagate and enforce OfBiz permissions, roles and users to JCR
- Expose the JCR part via WebDAV (and/or some RESTish service)
- JCR contents shall always be revisioned
- Prevent duplication of properties between OfBiz and JCR
- Explore Content Addressable Storage CAS options to prevent duplicate contents
- Use this opportunity to create a simple workflow for OfBiz CMS Contents (or externalize to a CMS that provides a workflow)