At 8/26/2004 11:19 PM, you wrote:
A JSR-168 portlet (or a set of them) is a complete webapp plus a configuration file! Pluto and therefore Cocoon uses the easiest way to handle this by using the servlet engine to deploy those portlet webapps - I don't know how other portal engines do it.
Yes. But I was under the impression that the portlet.xml file would exist within the Cocoon webapp along with all the portlets.
Well darn. I just reread the deployment chapter and now I see what I was missing. This makes it very hard for a standard servlet to be a portal unless it is also integrated with the servlet container.
