Christophe has been a silent member of the team for over a year now, quietly working away, and is long overdue to receive his recognition.
He has consistently been committing to Jetspeed CMS, on the mailing list discussing CMS issues, and helping out on general Jetspeed-1 support.
Some of you may be aware of the scratchpad/jetspeed-cms project under Jetspeed-1.
Christophe, mostly Christophe, and I have continued working on Jetspeed CMS over the last year.
We have completely refactored the original code, and it is now compatible with J2 and Pico components.
Jetspeed CMS (JCMS) will be a great addition to Apache Portals community.
It is not yet completed, so we are hoping to jump start the community again.
In short, JCMS is a framework for developing CMS/DMS applications in enterprise applications with a default solution for Jetspeed-2.
Its main goal is to provide clear interfaces to your enterprise code, but avoid strong couplings between your application and specific CMS technology.
There are a set of service components adhering to a set of JCMS interfaces: Model, Lock, Version, Security, Search, Index, Workflow, Event, Integration
JCMS is designed to work with with popular CMS products.
However it comes with a default OJB/J2-persistence relational database store.
A document describing JCMS can be found here:
http://cvs.apache.org/viewcvs.cgi/jakarta-jetspeed-2/docs/jcms2.pdf
-- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] [office] +01 707 773-4646 [mobile] +01 707 529 9194
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
