| Actually the "missing piece" of Jetspeed 2, Project Pluto, handles all the | dispatching on the portlets, in a model compatible with servlet containers | such as Tomcat. So yes, you are duplicating work that others have done, but | we are still waiting on the contribution of Pluto to the Apache Software | Foundation, which was developped by IBM as the Portlet API (JSR-168) | reference implementation, but that is currently undergoing legal work and | testing.
How's that coming along??
Unfortunately I don't know :) I think Scott Weaver has some contacts with the people at IBM in charge of this, but I don't think asking again would help. I'm sure that as soon as it is possible it'll become available.
I'm wondering: is Pluto compatible with -any- Servlet 2.3 impl, or does it tie into internals of Tomcat? I'm just trying to figure out how this Portlet spec (and Jetspeed, AND using Pluto in other portals) -really- will work..
My best guess is that Pluto makes heavy use of Servlet API 2.3 (and 2.4) request and response wrappers to communicate with web applications in a cross context manner. There will be problems sharing complex data, for example classes that are not available in both contexts, but apart from that it can work. There might be some portability issues because the use of wrappers is not implemented in a consistant way accross servlet containers.
The other alternative is to do something container specific, which would probably be more efficient in terms of speed, and make it available to Jetspeed as a JAR through the classpath. Now you could then call from Jetspeed something like :
PortletDispatcher.getInstance().lookupPortlet("rssPortlet).doView(RenderRequest, RenderResponse)
Actually this is probably the way the cross context dispatcher would make it's interface available, although it is not container specific.
Regards, Serge Huber.
- -- --- -----=[ shuber2 at jahia dot com ]=---- --- -- - www.jahia.org : A collaborative source CMS and Portal Server
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
