thanks, but its requires to create such code on every page
On Wed, Sep 30, 2009 at 19:38, Sergey Didenko 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:
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:
...
java:
@Parameter
private long someId
@Component
private
On Wed, Sep 30, 2009 at 3:52 PM, Thiago H. de Paula Figueiredo
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 uns
Em Wed, 30 Sep 2009 10:49:52 -0300, Massimo Lusetti
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
--
Th
On Wed, Sep 30, 2009 at 3:46 PM, Thiago H. de Paula Figueiredo
wrote:
> Em Wed, 30 Sep 2009 10:32:53 -0300, Andrey Larionov
> 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 sym
Em Wed, 30 Sep 2009 10:32:53 -0300, Andrey Larionov
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),
th
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 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
> item
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
You're welcome, hope this helps you to choose the good solution for your
needs.
2009/9/30 Andrey Larionov
> Thanks.
>
> On Wed, Sep 30, 2009 at 16:41, cordenier christophe
> wrote:
> > It also exists @Persist("client") to store the information directly in
> link
> > URLs
> >
> > And have a look
Thanks.
On Wed, Sep 30, 2009 at 16:41, cordenier christophe
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+
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:
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
wrote:
> Keep in mind that onActivate and onPassivate are called on pages not
> components.
> I you are trying to ac
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
> Also i have two components which works like described on page
> http://tapestry
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 me
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
> I want to create stateless application. Which aproach i should use.
>
> For
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 wrote:
> I want to create stateless application. Which aproach i should use.
>
> For example i have an some pagination compone
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 t
17 matches
Mail list logo
