I propose that we stop attempting to cache a Portlet. I can think of no reason why it would be a benefit. A Portlet cannot hold much in the way of instance variables, so it should not have any significant cost to construct.
There are many other objects that are constructed in the process of making a PortletSet to satisfy a request, and these are not cached. I'll be re-writing the JetspeedPortletFactoryService to introduce the PortletInstance over the next few days. This will touch the portlet caching code. - Glenn -------------------------------------------- Glenn R. Golden, Systems Research Programmer University of Michigan School of Information [EMAIL PROTECTED] 734-615-1419 -------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
