I understand that, per the portlet spec, Pluto makes a cross-context call to invoke portlets, even if the portlet resides in the same web application as Pluto itself. Unfortunately this also requires putting several JARs in Tomcat's shared\lib folder.

Is there any way around this? For the project I am working on, we prefer to deploy our application to our customers as a single self-contained WAR file without depending on any shared libraries outside the application. Is it possible to "short-circuit" Pluto so that it doesn't make a cross-context call to a portlet inside the same web-app as Pluto?

Any suggestions appreciated.

Thanks,
Rob

Reply via email to