The thing to remember is that Jackrabbit is nothing more than a content repository, like a database for your content. If we go the route of using a raw repository then we have to build a CMS application to sit on top of it.
What I am proposing is to use the work of others rather than build something new from the ground up. I don't know about you but designing content management systems isn't exactly my area of expertise. Last time I checked you can't even buy a book about using the JCR. Regards Scott On 20/06/2010, at 1:42 AM, Adrian Crum wrote: > I would be interested in helping out with integrating Jackrabbit with OFBiz. > > -Adrian > > --- On Fri, 6/18/10, Scott Gray <scott.g...@hotwaxmedia.com> wrote: > >> From: Scott Gray <scott.g...@hotwaxmedia.com> >> Subject: Hippo CMS >> To: dev@ofbiz.apache.org >> Date: Friday, June 18, 2010, 6:57 PM >> Anybody using or considered using >> Hippo CMS (onehippo.org) in conjunction with OFBiz? >> - Apache Licensed >> - Uses Jackrabbit as its repository >> - Supports Versioning, Internationalization, Publishing >> Workflows and more >> >> We could start out by using Hippo's UI to manage content >> and retrieve it for display within OFBiz using the JCR >> API. As the various document types needed by the OFBiz >> base applications begin to take shape we could look at ways >> to allow the content to be modified directly from within >> OFBiz (once again using the JCR API). >> >> Any thoughts, alternatives, ideas or whatever would be >> appreciated. I'm considering working on a POC in my >> spare time, not sure how long that might take at this >> stage. I already have a copy of Hippo running inside >> OFBiz but that was just a matter of expanding their WAR >> distribution and wrapping it in a component, next step would >> be gaining access to the repo from OFBiz code. >> >> Thanks >> Scott >> >> HotWax Media >> http://www.hotwaxmedia.com > > >
smime.p7s
Description: S/MIME cryptographic signature
