Some initial thoughts on the Jackrabbit integration... 1. Content Repository deployment model:
http://jackrabbit.apache.org/deployment-models.html I like the third model. OFBiz can treat the content repository the same way it treats datasources - if a content repository already exists then connect to it, otherwise start up an embedded content repository (Jackrabbit) and connect to it. 2. Using the Content Repository (CR) in OFBiz artifacts. We would want to retrieve content using existing OFBiz artifacts (screen widgets, Freemarker transforms, etc). This should be fairly straightforward - just create OFBiz artifacts that talk to the CR. The question is: Do we rewrite existing content artifacts (like the <content> screen widget), or do we create new content artifacts? The former will not be backward compatible and the latter would create duplication. Personally, I have no preference - I'm just tossing the question out there for further discussion. >From my perspective, if we could get a consensus on those two items, then the >Jackrabbit branch could be brought to a usable state fairly quickly. Then we >can attach a CMS system to it and see how things go. -Adrian
