Oops, I made one mistake in my previous response:
<snip/>
What about Jetspeed providing its own "PortletServlet" implementation.
The portlet servlet is pretty simple, initing the portlet, fixing up
the request and response and dispatching to the container.
Of course, we could even extend the Pluto PortletServlet for that end.
The problem is though, the current Pluto PortletServlet is completely
tied to the concrete PortalAdministrationService and PortletContextManager.
And as the container itself also requires the usage of these classes
(not interfaces) there is no point (yet) to do so.
Above I meant PortletDescriptorRegistry, not PortalAdministrationService.
Sorry about this.
Regards,
Ate
