You're correct, the PortalDriverServlet is the point of entry into the portal system. Once it receives a request, it gathers configuration information, processes any requested actions, and and determines which resource is used to generate content for that page (that's what pageConfig.getUri()). A request dispatcher is then retrieved for that resource, and the request is handed off to that for handling...
The configuration information which you're probably looking for (which is what populates pageConfig.getUri()) resides in WEB-INF/pluto-portal-driver-config.xml. This config file (amoung other things) defines the Pages and their backing uri which can be used to generate content. From this file, you can determine that "Test Page" is rendered by /WEB-INF/fragments/portlet.jsp.
Hope that helps,
David
On 11/4/05, Graham Klyne <[EMAIL PROTECTED]> wrote:
I think my question here would have an easy answer, if I knew where to look.
I'm trying to understand the flow of request handling in the test portal
whereby the initial test page is displayed for
http://localhost:8080/pluto/
I've traced the code (by static examination) through to a call of
PortalDriverServlet with the context URI http://localhost:8080/pluto/portal :
conf/localhost/pluto.xml
-> pluto-portal.war/index.jsp
-> redirect to http://localhost:8080/pluto/portal/
-> web.xml <servlet-mapping>
-> servlet plutoPortalDriver
-> web.xml <servlet> <servlet-name>
-> org.apache.pluto.driver.PortalDriverServlet.
Then I lose the trail, about:
[[
RequestDispatcher dispatcher = request.getRequestDispatcher(uri);
dispatcher.forward(request, response);
]]
I assume this has the effect of passing the request, via the portal
container, to the servlet that generates the page of test links, but I
can't find the logic that is being invoked to do this. What I'm
ultimately trying to do is locate the code that actually generates this
test page and the corresponding link target URIs, but I'd also like to
have a view of the internal logic that achieves this.
I think I'm maybe missing some key understanding about the details of
servlet dispatching. Can anyone offer any pointers, please?
#g
--
Graham Klyne
Research Technology Service
Oxford University Computing Services
