Pluto uses cross-context servlet dispatching to handle requests. In
other words, when a portal implementation which uses pluto recieves a
request, it hands the request off to the container which then retrieves
the target portlet's web app servlet context. Using this context, pluto
forward's the request to a "wrapper" servlet which invokes the portlet.
David
Kent Tong wrote:
Santiago Gala <sgala <at> apache.org> writes:
El sáb, 20-08-2005 a las 01:35 +0000, Kent Tong escribió:
Hi,
As the pluto portlet container is just a jar file, how does it
get control when a portlet app is trying to invoke a portlet?
Is there any hook in Tomcat specifically designed for portlet
containers to intercept the request?
Pluto is a portlet container, and it has a test/prototype portal
implementation. It is designed to be neutral for other portal
implementers, and so it is not designed as a "drop-in" war.
Thanks for the reply. Yes, I'm aware of that we need a portal
app to actually invoke a portlet. But what I'd like to know
is, when a portal app is trying to invoke a portlet, how can
pluto, the portlet container, get the opportunity to intercept
the request? In the same spirit, how is the code in the pluto
jar file get called so that it can read say WEB-INF/portlet.xml?
--
Author of an e-Book for learning Tapestry (http://www.agileskills2.org/EWDT)
