Ralph Goers wrote: > > In my patch I have it only scanning the current war file. I > don't know of any way to even get access to other webapps > from inside a war. Then again, I'm not sure why I'd want to > get to portlets from some other webapp. 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.
> > Also, how does that actually work? How does the portlet run > if it needs jars from the other webapp? Wouldn't you get a > ClassNotFoundException? You don't need classes etc. If a portlet is used the request is forwarded to the portlet webapp. So, currently only looking in the Cocoon war would break the JSR-168 feature. If you don't need JSR-168 portlets, you can use a different portal manager and turn off the support. However, the best solution would be a deployment functionality for JSR-168 in Cocoon. Carsten
