I seem to be explaining this concept a bit lately... perhaps the tapestry docs need to include an explanation.
Tapestry pages are singletons. Tapestry does a bit of byte code magic on your pages and components to transform them so that any request specific state is stored in a thread local map. In production mode, the member variables in your component classes are not used. In development mode, tapestry mirrors the thread local values to the component class fields to make debugging easier. http://tapestryjava.blogspot.co.uk/2010/07/everyone-out-of-pool-tapestry-goes.html -- View this message in context: http://tapestry.1045711.n5.nabble.com/Which-phase-of-page-lifecycle-will-not-occur-when-we-access-page-2nd-time-tp5718142p5718184.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
