I see, Nick. Things are much simpler with ActionLink because it isn't a
form component.
Thanks a lot!
Alex
-Original Message-
From: Nick Westgate [mailto:[EMAIL PROTECTED]
Sent: 08 August 2007 10:44
To: Tapestry users
Subject: Re: [T5] Submit control event handler cannot red
The natural flow of form submission is to update internal state with posted
values from the form and then render the result page.
Whether that is the same page (which is often the case) or not is usually
decided at the end of the form processing. So the select events simply notify
us of which sub
Thank you very much, Nick!
-Original Message-
From: Nick Westgate [mailto:[EMAIL PROTECTED]
Sent: 08 August 2007 10:21
To: Tapestry users
Subject: Re: [T5] Submit control event handler cannot redirect?
Think of it this way: the answer is "no" if you supply t:defer="false
es exactly
'select' event? What exactly we are selecting when pressing a Submit
button? Why its event is not 'action'?
-Original Message-
From: Denny [mailto:[EMAIL PROTECTED]
Sent: 08 August 2007 10:06
To: Tapestry users
Subject: Re: [T5] Submit control event handle
Think of it this way: the answer is "no" if you supply t:defer="false",
because then the redirect would occur before the form completed rewinding.
That would be kind of like an exception. ;-)
http://wiki.apache.org/tapestry/Tapestry5RedirectException
I agree with you that's it's inconsistent tho
The error message is clear. This type of event does not support return
values from
event handler methods.
Please take a look at http://wiki.apache.org/tapestry/Tapestry5HowToUseForms
Dealing with multiple submits Capter.
On 8/8/07, Kolesnikov, Alexander GNI <[EMAIL PROTECTED]> wrote:
>
> I am p
I am playing with a simple T5 application that has two pages: Start and
Another.
The Start page contains the following:
Display
Another page
And here is the page class contents:
@InjectPage
private Another anotherPage;
@OnEvent(value="submit", component="theForm"
