At 8/26/2004 10:54 PM, you wrote:
This is the way, Pluto works, so it just has been copied to
Cocoon. Somehow, the Cocoon portal has to know which JSR-168
portlets are available and this search mechanism tries
to look through all mounted webapps and extracts the portlet
information (if
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
At 8/26/2004 11:29 PM, you wrote:
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
Ralph Goers wrote:
However, the best solution would be a deployment functionality
for JSR-168 in Cocoon.
Do you have any suggestions on how this could be
accomplished? I'd be
happy to implement it, but using the services available to
servlets I'm not
sure how to do that. In fact,
Ralph Goers wrote:
I posted this last week and just want to make sure I'm not
doing anything wrong, as I plan to submit a patch as soon as
I verify that it works correctly (I'm not getting a
NullPointerException at startup at least).
I am trying to modify the pluto support so that it
