De : Ming Fai [mailto:mingfai@;hongkong.com] > > Another issue is, Jetspeed is supposed to be a portal server. > I personally > think it shouldn't be a CMS itself and it should be made to > integrated with > any CMS in the market. How do you think? >
I completely agree with this statement. It's only when you look at how you can achieve this goal that things start to be difficult: There's no single CMS API that can be used to code against so it would up to Jetspeed team to come up with a set of CMS portlets using a Jetspeed CMS abstraction API and write adapter modules to different CMS implementations. Definitely not a trivial task when you consider what functionality needs to be exposed in order to successfully integrate (user database and access rights for example) as well as the diversity of current CMS systems. Now if you have some CMS access APIs for Jetspeed, jetspeed-dev is waiting for you :) > btw, why this thread isn't in the Jetspeed developer list? > there should be > more Jetspeed experts there to comment. > AFAIK, all active committers are monitoring both which explains why you sometimes get dev discussions in the user mailing-list... -- Raphaël Luta - [EMAIL PROTECTED] Jakarta Jetspeed - Enterprise Portal in Java http://jakarta.apache.org/jetspeed/ -- To unsubscribe, e-mail: <mailto:jetspeed-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:jetspeed-user-help@;jakarta.apache.org>
