On 4/23/08, Thiago HP <[EMAIL PROTECTED]> wrote:
> You can use the @OnEvent(component = "componentName",
> value="eventName") annotation
>
> (http://tapestry.apache.org/tapestry5/apidocs/org/apache/tapestry/annotations/OnEvent.html)
> instead of method name conventions and then you can name yo
On 4/22/08, Kevin C. Dorff <[EMAIL PROTECTED]> wrote:
> NOW, to help with some future questions: With T3/T4 it was pretty easy to
> determine what methods to use for what, just look at the objects I was
> extending or implementing and I could see what method to implement or
> override to get w
I don't know of an extensive all-in-one-place list, but the documentation is
full of information about them all-- if you know where to look :-)
For Form related events, you're most likely interested in validating input:
http://tapestry.apache.org/tapestry5/tapestry-core/guide/validation.html --
in
Thanks for these suggestions. First Robert Zeigler, onValidateForm is exactly
what I needed, also I found the null-safe comparison was important.
Second, your suggest about disabling the submit javascript handler was right
on. The missing piece I put together was that my onValidateForm is always
Whoops... Peter is correct about the method/event name:
onValidateForm. Not onValidateFromForm, as I had posted, sorry.
Robert
On Apr 21, 2008, at 4/212:40 PM , Peter Beshai wrote:
You want to use onValidateForm to handle validation that involves
more than
one field.
Seems like the simples
You want to use onValidateForm to handle validation that involves more than
one field.
Seems like the simplest solution to your second problem is to use an
actionlink instead of a submit button and just have the fields reset by the
event handler. I believe t5-components has a button component that
On Apr 21, 2008, at 4/212:15 PM , Kevin C. Dorff wrote:
Sorry if these have been covered, I am somewhat new to T5, using
5.0.11.
First, onValidate seems to be called once for each form variable,
BEFORE the
setter is called for that form variable. While I understand that
logic, it
SEEMS
Sorry if these have been covered, I am somewhat new to T5, using 5.0.11.
First, onValidate seems to be called once for each form variable, BEFORE the
setter is called for that form variable. While I understand that logic, it
SEEMS makes things a touch difficult to check the value I want to valida
