that enables validation and decide
whether or not to do it.
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/form-field-validation-tp5511922p5512116.html
Sent from the Tapestry Users mailing list archive at Nabble.com
Hi there,
i search for a solution for the problem below:
i have a components that includes some form field components.
in one page i want to use this component with sone validations
and in an other page i want to use the same component but with
no validations.
how is the best way to solve this
If you validate server side its easy with onValidateFromSoAndSoField().
Then you just check your parameter that enables validation and decide
whether or not to do it.
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/form-field-validation-tp5511922p5512116.html
Sent
().
Then you just check your parameter that enables validation and decide
whether or not to do it.
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/form-field-validation-tp5511922p5512116.html
Sent from the Tapestry Users mailing list archive at Nabble.com
Hi all,
I am trying to understand how to implement custom validation of form fields.
Here's what I've got so far:
CreateAccount.java:
public class CreateAccount {
@InjectComponent
private Form createAccountForm;
@OnEvent(value = validate, component = createAccountForm)
void
Hello Marc,
I think you want the @Component annotation instead of
@InjectComponent. The latter is Used exclusively inside a mixin to
connect the mixin to the component to which it is attached.[1]
I haven't tested whether this will solve your problem, but it seems likely.
A good starting point
PROTECTED]
To: Tapestry users users@tapestry.apache.org
Sent: Saturday, September 29, 2007 19:40
Subject: Re: T5 form field validation, component injection
Hello Marc,
I think you want the @Component annotation instead of
@InjectComponent. The latter is Used exclusively inside a mixin