I vote for that. It makes sense and would make initialization from a database easier and more consistent. I end up doing it in onActivate since it's called for form submission and regular rendering.
Norman Franke Answering Service for Directors, Inc. www.myasd.com On Nov 21, 2012, at 3:09 PM, Howard Lewis Ship wrote: > However, I'm thinking of "de-deprecating" @PageAttached and @PageDetached. > I think they are actually useful in the long run. > > So: > > @PageLoaded - once when the page is initially constructed > @PageAttached - once per request, when the page is first used in that > request > @PageDetached - once per request, after the response has been sent to the > client user agent > > > On Wed, Nov 21, 2012 at 12:43 AM, Lance Java <lance.j...@googlemail.com>wrote: > >> @PageAttached and @PageDetached are deprecated and are leftovers from page >> pooling. The page pool has been disabled by default since version 5.2 in >> favour of page singletons which maintain mutable state in thread local >> maps. >> >> >> >> -- >> 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-tp5718142p5718144.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 >> >> > > > -- > Howard M. Lewis Ship > > Creator of Apache Tapestry > > The source for Tapestry training, mentoring and support. Contact me to > learn how I can get you up and productive in Tapestry fast! > > (971) 678-5210 > http://howardlewisship.com
