I just had a look again at a heap from our app and one common source to all the components instances is the object pool. http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/tapestry-framework/src/java/org/apache/tapestry/services/impl/ObjectPoolImpl.java?view=markup The code says "** This ia a minimal implementation, one that has no concept of automatically removing unused pooled * objects. Eventually, it will also register for notifications about general cache cleaning."* ** This sounds scary... Does anyone know exactly what the role of this class is? Somehow this class can hold references to page instances (which hold component instances). Could this pool use weakreferences or at least have a limit?
-- Thanks, Henri.
