Slide/Turbine/Jetspeed integration

[cl...@netscape.net]

Still working on a complete integration between Slide & Turbine/Jetspeed. If you want more info or help me, just send me a mail.

Status : on experience. I start the coding but it is not complete.
The most important phases, I see :

Phase 1 :    Turbine/Slide integration
---------------------------------------


A. Building  a new Turbine service used to access to a CMS repository


  1. Generic interface for a content management system
    

  2. Concrete implementation of the CMS interface for Slide

     note : Maybe we can increase the quality of the current code. 
            Not all CMS features are implementing in this class - for the moment


  3. New Turbine service in order to access to the CMS component

     note : this service will delegate the job to the CMS component. It is just the link between Turbine & the CMS component.


B. Building controller classes
  
   note :   
      * Get the CMS repository data from the turbine CMS service and put it in a View (Velocity,JSP, ...) context.
      * Avoid screen class in Turbine. I have something to submit you.
      * Use the pull service

C. Building Views

  1. View for the end-users : 
     * Display the CMS tree in function of the security policy & preferences = content personnalisation
     * Add a new content, create catalog, ...
     * Display meta data (content locked, security info, ...)
     * workflow & notification 

  2. View for the administrator


D. Configuration/install


Phase 2:   Integration with Jetspeed
------------------------------------

A. Building end-user CMS portlets (display a catalog, add a new content, create a new version, notification, ...)

B. Building admin CMS portlets (security setting, ...)



Christophe
__________________________________________________________________
Get your own FREE, personal Netscape Webmail account today at http://webmail.netscape.com/