Got some patience left for another question ? :) So now with 5.3.6, since pooling is disabled, is it a single page instance for each request ? And how does it differ from the activation context event if they are both executed when the page is first loaded ?
My *guess* is that tapestry loads the page for the first time (@PageLoaded), attaches it to the client's session (that is created by default) and then executes the ActivationContext even whenever a request is made to the page, am I correct ? On Thu, Nov 22, 2012 at 7:22 AM, Athneria, Mahendra < mahendra.athne...@atos.net> wrote: > Thanks a lot Howard Lewis for your valuable comment :-). > > Regards, > Mahendra > > -----Original Message----- > From: Howard Lewis Ship [mailto:hls...@gmail.com] > Sent: Thursday, November 22, 2012 1:41 AM > To: Tapestry users > Subject: Re: Which phase of page lifecycle will not occur when we access > page 2nd time? > > 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 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >