afaik all properties are reset to their initial value (defaults to null) when the page is returned to the pool ...
> -----Original Message----- > From: Nick Faiz [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 11, 2006 7:43 AM > To: Tapestry users > Subject: Best practice? Cleaning up instance data in pages and > components for the cache? > > > Hi, > > Is there an easyt practice for ensuring that instance data in pages > and components is cleaned up, before the object is cached for future > needs? > > My current idea is to implement the detach() method in each page and > have the components implement PageDetachListener. > > Is there a more convenient solution which would save this > extra work? > Most of the time Im relying on ASO objects and local var.s in > methods, rather than class data, but perhaps there is a 'clean up' > tactic which can run on a bunch of components, like an interceptor > which can scan the components for public setters to nullify, etc.? > > Nick Faiz, > Developer > www.q9software.com > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
