On Jun 30, 2004, at 8:12 AM, Scott T Weaver wrote:
Could you explain this serious issue in a little more detail?We are caching both PortletEntities and PortletWindows.
This is becoming a serious issue with regards to re-deployment breaking because of stale objects within misc. caches.
I can't re-deploy here, because of a resource leak holding on to the jar file
Its not clear what exactly the problem is from your description above, or if its related to the resource leak bug
Is it because the portlet gets a new id, and the entity still points to the old id?
If the portlet knew about all of its entities, it could invalidate them
Funny you mention that, I reviewed Open Symphony's oscache last night1. (Not so good approach) Expose both window and entity caches as components so that they are accessible by any components that need to manipulate the caches, like deployment.
2. (Better approach) Same as above, but use a single cache via a caching
api like OSCache, http://www.opensymphony.com/oscache/
I was looking into putting a cache into the Profiler after looking at the Proxy Tools bug that Jeremy reported
There is also
http://jcache.sourceforge.net/
and from Apache
http://jakarta.apache.org/turbine/jcs/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
