See
http://tapestry.apache.org/tapestry4.1/apidocs/org/apache/tapestry/form/validator/Validator.html
Probably just override getAcceptsNull()
On Fri, Mar 6, 2009 at 7:21 PM, Ivano Luberti lube...@archicoop.it wrote:
Hello, we are using T4.1
We have to validate a form and we don't want to do it
Ok, thanks to all of you: it seems that my first email got unnoticed but
now I have plenty to read :-D
The renderError in the form componet would seem exaclty what we would
need but unfortunately we are using T4.1
So I will have a look at the Va.lidationDelegate usage suggested by
Jonathan.
Sorry to ask for this again, but I have seen no answer.
I will get no answer again I will stop asking for this, of course.
TIA
Hello, we are using T4.1
We have to validate a form and we don't want to do it client side.
Let say we have three text fields.
The validation should
.
Read the docs on the Form component, and see the examples in the user
guide.
Cheers
-Original Message-
From: Ivano Luberti [mailto:lube...@archicoop.it]
Sent: Monday, March 09, 2009 8:30 AM
To: Tapestry users
Subject: cross field validation with empty fields
Sorry to ask for this again
-
From: Ivano Luberti [mailto:lube...@archicoop.it]
Sent: Monday, March 09, 2009 8:30 AM
To: Tapestry users
Subject: cross field validation with empty fields
Sorry to ask for this again, but I have seen no answer.
I will get no answer again I will stop asking for this, of course.
TIA
Em Mon, 09 Mar 2009 14:08:43 -0300, Luther Baker lutherba...@gmail.com
escreveu:
Oddly enough, it is NOT the validation handler I want to bring to your
attention to (here on this validation.html page :) and again, obviously,
this is Tapestry 5 - but notice how authentication is done in the
validation with empty fields
Em Mon, 09 Mar 2009 14:08:43 -0300, Luther Baker lutherba...@gmail.com
escreveu:
Oddly enough, it is NOT the validation handler I want to bring to your
attention to (here on this validation.html page :) and again,
obviously,
this is Tapestry 5 - but notice how
That's a fine point to clarify.
My underlying suggestion wasn't meant to imply which was the correct,
well-defined event to handle. This is the second post ... no luck/help so
far? ... So my suggestion is that, if all else fails, you can do MANUAL
validation in, if nothing else, the MAIN event
My experience was with 4.0.
You want to look at the ValidationDelegate.
@Bean
public abstract ValidationDelegate getDelegate();
// set up as listener for form
public void onSubmit(IRequestCycle cycle){
ValidationDelegate = getDelegate();
(if (delegate.getHasErrors())
return;
if
Oops sorry @Elmer, I mistyped your name in the previous post and meant
@Ivano.
Also, @Elmo, I think you're suggestion was perfect! but it looked like T5
code.
Shows how little I know about T4 though. Sorry - I think your post was right
on if all those annotations and events were in T4.
-Luther
a RedirectException
}
}
I just thought the poster might still be pondering what to do in T4.
Cheers,
Elmer
-Original Message-
From: Luther Baker [mailto:lutherba...@gmail.com]
Sent: Monday, March 09, 2009 1:49 PM
To: Tapestry users
Subject: Re: cross field validation with empty fields
Oops
Cool beans. Literally :)
On Mon, Mar 9, 2009 at 12:49 PM, Jonathan Barker
jonathan.theit...@gmail.com wrote:
My experience was with 4.0.
You want to look at the ValidationDelegate.
@Bean
public abstract ValidationDelegate getDelegate();
// set up as listener for form
public void
Thanks Elmer. And ugh ... sorry for the previous typo @Elmo,
(Cool Beans was @Jonathan for his Bean example - but got out of order in
this thread).
-Luther
On Mon, Mar 9, 2009 at 1:02 PM, Luther Baker lutherba...@gmail.com wrote:
Cool beans. Literally :)
On Mon, Mar 9, 2009 at 12:49 PM,
Hello, we are using T4.1
We have to validate a form and we don't want to do it client side.
Let say we have three text fields.
The validation should implement the following rule:
if (fielda=) (fieldb= || fieldc=)
then throw new Exception();
The problem is that we cannot link the validation to
14 matches
Mail list logo
