If you use non-abstract getter/setter methods, you need to take care of initializing variables (in detach() method of page). On the other hand if property-specification is used, tapestry takes care of initialization/reset.
This happens because of page object pooling. -----Original Message----- From: hari ks [mailto:[EMAIL PROTECTED] Sent: 07 August 2005 10:51 To: tapestry-user@jakarta.apache.org Subject: tapestry CACHING issue - coding guidelines hi, We recently had a tapestry caching issue. Whatever user enters in a page becomes visible another user who comes to that page. This was probably because of class variables being used in page class. We converted all concrete getter/setter used in html to abstract and put them as property-specifications in .page file. This seems to eliminate caching issue. Wanted to confirm whether this is the right way. Also want to know, if we need to convert non-abstract getter/setter of components also to abstract getter/setter(and add property-specification to .jwc file). please provide your valuable suggestions. Our application cannot go to production with these issues. Thanks, Hari. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
