I wrote a paging component that I think would do what you want. The component takes a PageSource implementation which acquires the paged list of items for display and also constructs the page activation context for any paging links - so there's no need for any @Persist annotations.
Here's my blog post if you want to take a look: tapestry paging component<http://norobotblog.blogspot.com/2009/09/leaf-super-easy-paging-for-tapestry5.html> Cheers, Jack On Wed, Sep 30, 2009 at 1:41 PM, cordenier christophe < christophe.corden...@gmail.com> wrote: > It also exists @Persist("client") to store the information directly in link > URLs > > And have a look at this, this is the topic i was talking about > > > http://markmail.org/search/?q=list%3Aorg.apache.tapestry.users+onactivate+component#query:list%3Aorg.apache.tapestry.users%20onactivate%20component+page:1+mid:mqs3srsveutjt4mu+state:results > > 2009/9/30 Andrey Larionov <anlario...@gmail.com> > > > But Pages is Components. As i understand there are no distinction. Or i'm > > wrong. > > > > So there no so simple way to drop persistence? > > > > On Wed, Sep 30, 2009 at 16:30, cordenier christophe > > <christophe.corden...@gmail.com> wrote: > > > Keep in mind that onActivate and onPassivate are called on pages not > > > components. > > > I you are trying to activate/passivate components , I think there is > > current > > > post on the user mailing list. > > > > > > 2009/9/30 Andrey Larionov <anlario...@gmail.com> > > > > > >> Also i have two components which works like described on page > > >> http://tapestry.apache.org/tapestry5.1/guide/pagenav.html > > >> in section "component event requests / Persistent Data". > > >> On components sets data in another. Can i replace persistency in this > > >> place by onActivate/onPassivate? > > >> I implement this methods, but they never called. > > >> > > >> On Wed, Sep 30, 2009 at 14:52, cordenier christophe > > >> <christophe.corden...@gmail.com> wrote: > > >> > Hello > > >> > > > >> > Have a look at the LinkCreationListener which can be used to add > > custom > > >> > parameters. > > >> > If you couple this to a Per-thread service you can achieve to pass > > data > > >> from > > >> > one request to another. > > >> > > > >> > 2009/9/30 Andrey Larionov <anlario...@gmail.com> > > >> > > > >> >> I want to create stateless application. Which aproach i should use. > > >> >> > > >> >> For example i have an some pagination component similar to > GridPager, > > >> >> but less coupled to paginating component. In Tapestry current page > is > > >> >> stored in Persist field. WHat is alternative solution? Can i use > > >> >> onActivate/onPassivate to store value across requests produced by > > >> >> clicking on a page link? > > >> >> > > >> >> Thank > > >> >> > > >> >> PS. Sorry for my english. Please ask questions if something is > > >> >> ununderstandable, i'll try to explain it broader. > > >> >> > > >> >> > --------------------------------------------------------------------- > > >> >> 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 > > >> > > >> > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > >
