It seems that PageAttached was un-deprecated in 5.4 some time ago, however I am not sure about the motivation:
https://apache.googlesource.com/tapestry-5/+/0998b92d51d475ed20fa5aadea06bc5bd37c39a8%5E%21/ I believe that PageAttached can still be useful even when there is no page pool. The code still can set internal component fields with some dynamic values, even if actually it sets some request attributes. PageAttached is a bit more comprehensive than onActivate() because can be implemented by components and non-active pages. On Tue, Apr 14, 2015 at 11:50 PM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > On Tue, 14 Apr 2015 14:05:33 -0300, Cezary Biernacki <cezary...@gmail.com> > wrote: > > Hi Тимур, >> Have you tried putting your asynchronous in pageAttached() methods (also >> see @PageAttached annotation) in your components? >> >> https://tapestry.apache.org/page-life-cycle.html >> >> However pageAttached is invoked on all pages that are somehow involved in >> the request processing (e.g. they are referenced via PageLink component) >> > > @PageAttached only makes sense in a page pool and Tapestry doesn't use one > since 5.2. I guess its undeprecation was a mistake. Or I have no idea why > that happened. > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
