LOMBART Christophe wrote:
Hi All,
As you certainly know, we are building the CMS solution for Jetspeed 2 (JCMS). This project should availabe in Incubator ASAP. In this context, I want to start a discusion thread on this topic. My goal is to check with committers & the Jetspeed users if JCMS fits your needs. So, this mail will resume the main JCMS features and explain a little bit the service architecture.
Free freel to ask all questions or suggestions you want. JCMS will certainly offers an great perspective to your Jetspeed application. So, you are welcome to contribute.
Of course I would like to be a committer on this project ;)
Kind regards,
Christophe
JCMS Overview and features : --------------------------------------
See on http://wiki.apache.org/incubator/JcmsProposal.
JCMS Service Architecture : ---------------------------------
* The JCMS components can be running on a Spring engine or any other kind of IOC container. So, it is quite easy to integrate JCMS into Jetspeed 2.
* JCMS is divided into different layers : + JCMS Services: There is one service per CMS activities : Structure/model, versionning, searching/indexing, security, workflow, ....
+ The Persistence Service : All JCMS services delegates requests like create document, get folder children,... to the persistence service. Depending on the requests info, the persistence store try to find the correct JCMS store & dispatch the request to this one (see below).
+ The JCMS Stores : A JCMS store is a plugin used to by the persistence store in order to used the correct API with the desired content server. For example, we can imagine to have a webdav store plugged into JCMS and another one which is used to access to a propriatary content server. Currently there is a simple OJB store. a Webdav store is under construction. Later, we will be build a JCR store.
* The security service is completly based on J2 security services. You will find in the JCMS project a small document which explain in more details the security implementation (fine grained access control, ...).
Notes :
* It is important to note that the JCR integration will be done across a new kind of store. Another solution is to replace the persistence service by a complete JCR implementation.
In short term, we choice the first solution because JCR implementations are quite new and we want to support a large kind of content store API. Providing our own persistence service is a garantee to support a more important number of content store type (webdav, commercial product API, ...). Maybe later, this part of the design will be changed.
* Gouping together different kind of store is a great challenge. We are looking for guys who can help with the JCR integration.
JCMS Status :
-----------------
Cerainly, the first question is : what about the developement status ? Hum ! it is a good question, we NEED committers. Again, you are welcome to contribute.
The most important services are almost done. We have to fix some bugs and makes more unit tests.
What is currently missing : * Services : workflow + Event handler
* Portlets : Plan to start some admin portlet and simple content editor ASAP. A Jetspeed demo application will be provided. We want also to build some specific portlets application like JcmsNews, JcmsForum, ...
I've started on converting a J1 portlet that can navigate of a JCMS-1 hierarchy. The portlet is velocity-based, it will need the base Velocity bridge in place first.
-- 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]
