For example; @PageAttached could be a good place to obtain a connection to a database, and @PageDetached could be a place to close that connection.
However, a per-thread service would usually be a better solution, and would be lazy (not created until needed). So, I think @PageAttached and @PageDetached can wait on the wall for 5.4 and be fully restored or fully removed in 5.5. On Wed, Nov 21, 2012 at 1:33 AM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > On Wed, 21 Nov 2012 05:07:19 -0200, Athneria, Mahendra < > mahendra.athne...@atos.net> wrote: > > Hi, >> > > Hi! > > > I have one question regarding the Page life cycle. >> >> When we are accessing the page very first time then it will follow below >> life cycle. >> > > @PageLoaded. As Lance said @PageAttached and @PageDetached shouldn't be > used because they only made sense when Tapestry still pooled page class > instances. > > What exactly are you trying to do? Probably you don't even need to use > @PageLoaded. > > -- > Thiago H. de Paula Figueiredo > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@tapestry.**apache.org<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
