> That's not true for @PageLoaded that's where you put "one-time > component initializations that can't be done at instantance > initialzation time"
Yes I see that I have missed that. ----- Original Message ----- From: "Massimo Lusetti" <mluse...@gmail.com> To: "Tapestry users" <users@tapestry.apache.org> Sent: Friday, 19 June, 2009 18:53:19 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: RenderSupport in pages? On Fri, Jun 19, 2009 at 5:46 PM, <p.stavrini...@albourne.com> wrote: > > > Request != render. A request can have rendering, but their not the same. > Yes of course, I was talking about the scope of the service "Environmental > services are, by their nature, per-thread (and therefore per-request).", so > are @PageAttached and @PageLoaded triggered on every Request. That's not true for @PageLoaded that's where you put "one-time component initializations that can't be done at instantance initialzation time" Cheers -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
