> 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 :) >
I wonder this is the thing we're looking for: http://www.jcp.org/jsr/detail/170.jsp if so, let's wait for it to be finalized. In the forum in the jcr.day.com, there was once a message (that show to public, at that time) that got a link to javadoc of day's product. If someone is going to develop something before the JSR 170 is done, he may reference to the API of major CMS vendors. > > 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... > Indeed, I was not so serious when asking the question. regards, mingfai -- To unsubscribe, e-mail: <mailto:jetspeed-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:jetspeed-user-help@;jakarta.apache.org>
