You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Andrey Larionov <an...@gmail.com> on 2009/09/30 12:45:02 UTC
About stateless applications
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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: About stateless applications
Posted by Andrey Larionov <an...@gmail.com>.
thanks, but its requires to create such code on every page
On Wed, Sep 30, 2009 at 19:38, Sergey Didenko <se...@gmail.com> wrote:
> is to pass page activation context as action
> context, then initialize and return component as AJAX response:
>
> The code may require some cleanup, but the idea is the following:
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: About stateless applications
Posted by Sergey Didenko <se...@gmail.com>.
Another alternative is to pass page activation context as action
context, then initialize and return component as AJAX response:
The code may require some cleanup, but the idea is the following:
tml:
<form t:id="form1" t:type="Form" t:context="someId" t:zone="someZone-${someId}">
...
java:
@Parameter
private long someId
@Component
private TestComponent testComponent;
protected void setupRender() {
// that is called during page request
testComponent.set( getSomeIdFromPageActivationContext() );
}
Object onSubmitFromForm1( long someId ) {
// setupRender is not called for AJAX request
// so we pass someId as action context here
if ( request.isXHR() ) {
testComponent.set( someId );
return testComponent;
} else {
return null;
}
}
On Wed, Sep 30, 2009 at 3:41 PM, cordenier christophe
<ch...@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 <an...@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
>> <ch...@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 <an...@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
>> >> <ch...@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 <an...@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-unsubscribe@tapestry.apache.org
>> >> >> For additional commands, e-mail: users-help@tapestry.apache.org
>> >> >>
>> >> >>
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> >> For additional commands, e-mail: users-help@tapestry.apache.org
>> >>
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: About stateless applications
Posted by cordenier christophe <ch...@gmail.com>.
You're welcome, hope this helps you to choose the good solution for your
needs.
2009/9/30 Andrey Larionov <an...@gmail.com>
> Thanks.
>
> On Wed, Sep 30, 2009 at 16:41, cordenier christophe
> <ch...@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 <an...@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
> >> <ch...@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 <an...@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
> >> >> <ch...@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 <an...@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-unsubscribe@tapestry.apache.org
> >> >> >> For additional commands, e-mail: users-help@tapestry.apache.org
> >> >> >>
> >> >> >>
> >> >> >
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >> >> For additional commands, e-mail: users-help@tapestry.apache.org
> >> >>
> >> >>
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail: users-help@tapestry.apache.org
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: About stateless applications
Posted by Andrey Larionov <an...@gmail.com>.
Thanks.
On Wed, Sep 30, 2009 at 16:41, cordenier christophe
<ch...@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 <an...@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
>> <ch...@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 <an...@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
>> >> <ch...@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 <an...@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-unsubscribe@tapestry.apache.org
>> >> >> For additional commands, e-mail: users-help@tapestry.apache.org
>> >> >>
>> >> >>
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> >> For additional commands, e-mail: users-help@tapestry.apache.org
>> >>
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: About stateless applications
Posted by Massimo Lusetti <ml...@gmail.com>.
On Wed, Sep 30, 2009 at 3:52 PM, Thiago H. de Paula Figueiredo
<th...@gmail.com> wrote:
> Of course, we could implement that too. Any implementation hints? :D
I'm sorry i don't go that further :)
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: About stateless applications
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
Em Wed, 30 Sep 2009 10:49:52 -0300, Massimo Lusetti <ml...@gmail.com>
escreveu:
> We definitely should rise a vote for a configuration symbol:
> tapestry.make-my-life-easier to be set default to true :)
Tapestry already does that, no? :)
Of course, we could implement that too. Any implementation hints? :D
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: About stateless applications
Posted by Massimo Lusetti <ml...@gmail.com>.
On Wed, Sep 30, 2009 at 3:46 PM, Thiago H. de Paula Figueiredo
<th...@gmail.com> wrote:
> Em Wed, 30 Sep 2009 10:32:53 -0300, Andrey Larionov <an...@gmail.com>
> escreveu:
>
>> Thanks, but my interest not only in pager, but in creating complex
>> stateless apllications easy
>
> It's not documented, but there is a configuration symbol
> (tapestry.persistence-strategy, SymbolConstants.PERSISTENCE_STRATEGY), that
> defines the persistency strategy for fields annotated with @Persist (without
> specifying a strategy like flash or session). Maybe you could use it to make
> Tapestry use client persistence by default. I haven't tested this, though.
We definitely should rise a vote for a configuration symbol:
tapestry.make-my-life-easier to be set default to true :)
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: About stateless applications
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
Em Wed, 30 Sep 2009 10:32:53 -0300, Andrey Larionov <an...@gmail.com>
escreveu:
> Thanks, but my interest not only in pager, but in creating complex
> stateless apllications easy
It's not documented, but there is a configuration symbol
(tapestry.persistence-strategy, SymbolConstants.PERSISTENCE_STRATEGY),
that defines the persistency strategy for fields annotated with @Persist
(without specifying a strategy like flash or session). Maybe you could use
it to make Tapestry use client persistence by default. I haven't tested
this, though.
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: About stateless applications
Posted by Andrey Larionov <an...@gmail.com>.
Thanks, but my interest not only in pager, but in creating complex
stateless apllications easy
On Wed, Sep 30, 2009 at 17:20, Jack Nuzbit <fn...@googlemail.com> wrote:
> rote 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: About stateless applications
Posted by Jack Nuzbit <fn...@googlemail.com>.
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.cordenier@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 <an...@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
> > <ch...@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 <an...@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
> > >> <ch...@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 <an...@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-unsubscribe@tapestry.apache.org
> > >> >> For additional commands, e-mail: users-help@tapestry.apache.org
> > >> >>
> > >> >>
> > >> >
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > >> For additional commands, e-mail: users-help@tapestry.apache.org
> > >>
> > >>
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
Re: About stateless applications
Posted by cordenier christophe <ch...@gmail.com>.
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 <an...@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
> <ch...@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 <an...@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
> >> <ch...@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 <an...@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-unsubscribe@tapestry.apache.org
> >> >> For additional commands, e-mail: users-help@tapestry.apache.org
> >> >>
> >> >>
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail: users-help@tapestry.apache.org
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: About stateless applications
Posted by Andrey Larionov <an...@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
<ch...@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 <an...@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
>> <ch...@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 <an...@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-unsubscribe@tapestry.apache.org
>> >> For additional commands, e-mail: users-help@tapestry.apache.org
>> >>
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: About stateless applications
Posted by cordenier christophe <ch...@gmail.com>.
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 <an...@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
> <ch...@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 <an...@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-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail: users-help@tapestry.apache.org
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: About stateless applications
Posted by Andrey Larionov <an...@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
<ch...@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 <an...@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-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: About stateless applications
Posted by cordenier christophe <ch...@gmail.com>.
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 <an...@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-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: About stateless applications
Posted by Robin Komiwes <od...@gmail.com>.
Storing the value using onActivate/onPassivate should effectively work. But
you will need to implement a new grid pager.
On Wed, Sep 30, 2009 at 12:45 PM, Andrey Larionov <an...@gmail.com>wrote:
> 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-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>