Ah yes, that's for data represented by an abstract getter and setter,
right?
I'm discovering that there's a hybrid solution to this - rely on
those abstract proxies whenever possible, dont use class members,
store state in an ASO. :)
Cheers,
Nick
On 11/04/2006, at 3:52 PM, Schulte Marcus wrote:
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: tapestry-user-
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Nick Faiz,
Developer
www.q9software.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
