PropertyFinder cache grows without bound.

[Kim Dykeman <kd...@mediabolic.com>]

Hi,

I ran into an "OutOfMemory" situation the other day and tracked it down
to the static _cache field in
org.apache.tapestry.util.prop.PropertyFinder.  In the end I realized
that the problem was related to having several stateful components that
should have been configured as stateless on several pages.

In following through the codepath by which references landed in the
cache, I was wondering what a more appropriate behavior might be.

After searching the list archives a bit, I found a message from a list
member who apparently encountered the same issue
("http://article.gmane.org/gmane.comp.jakarta.tapestry.devel/1103/match=propertyfinder+cache").

In addition to the possibilities mentioned in the above referenced
posting, I was wondering if it would make sense to have two caches?... 
One for caching stateless components (on a global/static basis) and a
second cache tied to a user's http session for stateful components (i.e.
implementing HttpSessionBindingListener).

Thanks in advance for any feedback or suggestions.

-Kim


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org