Hi Scott,
I think in principle you are right-- I have been heavily reading (maybe too much) into the WebSphere Portlet development guide v4.1 and in Section 6.3 where they describe the relation between web.xml and the portlet.xml there is a mapping between portlets defined as servlets in the web.xml and the portlet deployment descriptor. In WebSphere at least, it seems the init params for the PortletConfig object are defined as the init params coming from the portlet/servlet entry in the web.xml. Maybe a lot of this is just implementation dependent. For instance, I've decided to take the route that portlets aren't really servlets, so I will define PortletConfig parameters in my portlet.xml not any web.xml.
Jason
I don't think this is the idea. Nowhere did I read that the actual servlet container was to be responsible for managing portlets nor would they be registered via the web.xml file. I think the idea was to reuse common method signatures that applied both to portlets and servlets. Portlets themselves will be managed by a portlet container not by the servlet container.
Scott
-- To unsubscribe, e-mail: <mailto:jetspeed-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:jetspeed-dev-help@;jakarta.apache.org>
