>
> I beg to differ. The framework itself does not use the session. If you're
> using an onActivate()/onPassivate() method pair, you don't need to persist
> the corresponding fields.
ActionLink and EventLink preserve the page context as long as you provide it
> to the context parameter.
>
After y
Em Wed, 09 Dec 2009 15:34:52 -0200, kamiseq escreveu:
The session itself is extremely overused in the framework and it could be
limited if only actionLink's call preserve page's context.
I beg to differ. The framework itself does not use the session. If you're
using an onActivate()/onPassiv
>
> I don't understand what's your problem. Page activation context would
>> always be kept between any requests of the same page, if you add the context
>> that given to the tab component tot he page activation conetext, and provide
>> the correct onActivate and onPassivate handler, there would b
Em Wed, 09 Dec 2009 12:44:31 -0200, ningdh escreveu:
I don't understand what's your problem. Page activation context would
always be kept between any requests of the same page, if you add the
context that given to the tab component tot he page activation conetext,
and provide the correct o
ould be no problem at all.
Everything should work.
DH
- Original Message -
From: "kamiseq"
To: "Tapestry users"
Sent: Wednesday, December 09, 2009 6:40 PM
Subject: Re: t5 handling events by components, event handling sequence
yes eventually I did so
*BUT* answering yo
yes eventually I did so
*BUT* answering your question, it -in my opinion- how tab component renders
doesn't depend on page context, because it just groups/organise content of
the page and if removed page remains unchanged. component model depends on
context but it is given by page and component is
Why don't you want to pass the page's context to the tab component? Isn't the
content of the tabs dependent on the value of the page's context?
On 09/12/2009, at 4:46 AM, kamiseq wrote:
> ok one more thing, my tabs are working great but let examine such a usecase
>
> 1)I have user page with a g
ok one more thing, my tabs are working great but let examine such a usecase
1)I have user page with a grid of a user list
2)when user is selected I rerender the page with context specified by grid
element
3)my url then is something like myapp/user/1 and the tab control is
displayed with 3 tabs (fo
yep
I am just after huge argument with my firend about tapestry and wishes vs
reality :)
now I understand and it makes some sense although I try to avoid @persist as
much as possible
and the main problem here is to define how user must use the page and
interact with it and what if session expires
Em Mon, 07 Dec 2009 21:38:17 -0200, kamiseq escreveu:
hi,
Hi!
I ve wrote simple component that renders link and handles event
triggered by
the link then it sets some value and should render that value.
the problem is that I get the value but then the value is lost as
tapestry redirects
Ok,
but how can I command the component to render actionLink as a link to the
page that contains the component or how could I redirect from component to
the page in generic way(Could I pass any reference of the page as
component's parameter? and then use public method on that page?)? any way to
int
activation context.
DH
http://www.gaonline.com.cn
- Original Message -
From: "kamiseq"
To:
Sent: Tuesday, December 08, 2009 7:38 AM
Subject: t5 handling events by components, event handling sequence
hi,
I ve wrote simple component that renders link and handles event trigge
hi,
I ve wrote simple component that renders link and handles event triggered by
the link then it sets some value and should render that value.
the problem is that I get the value but then the value is lost as tapestry
redirects to a page that holds the component
Tabs is the page that renders TabN
13 matches
Mail list logo