That must be the point, of course.
But why are form fields implemented in different ways?
There are fields like ie TextField, that record their input value
into the trackings, even if there was no error.
On the other side, PropertySelection or Checkbox, record only errors
into the tracking
My guess is that you won't need those fields unless you have some error
to show and you want to tell the user which field was wrong.
If this is the idea for the most common use of field validation, the
consequence is that you don't want to take note of unused data.
Ivano Pagano.
Christian Mitt
Have you looked at IValidationDelegate? You can extend
ValidationDelegate and override methods such as writeSuffix to add
error messages around where the field is rendered. This will work out
of the box for the fields you mentioned that already support
validation. For checkboxes, radio, and list bo
Am 01.02.2006 um 01:56 schrieb Christian Mittendorf:
That might be a solution: do ValidPropertySelection and
ValidCheckbox record their input values to the ValidationDelegate
in any case, even if no error occured?
Thanks for the hints!
I've implemented both classes and added the following c
Ah cool, thanks for the link, I'm not sure how I missed that one :P
- Original Message -
From: "Christian Mittendorf" <[EMAIL PROTECTED]>
To: "Tapestry users"
Sent: Tuesday, January 31, 2006 5:13 PM
Subject: Re: Using fieldTrackings
Am 01.02.2006
Am 01.02.2006 um 02:03 schrieb Daniel Lydiard:
When ever a user chooses the "noSelectionValue" which is the
default, it's recorded in the validation delegate.
Is this what you're going for?
No, not really (I do also need the selected value in the validation
delegate). But the hints and i
ValidatorException in
rewindFormComponent()). It was pretty straight forward.
Is this what you were going for?
- Original Message - From: "Christian Mittendorf"
<[EMAIL PROTECTED]>
To: "Tapestry users"
Sent: Tuesday, January 31, 2006 4:34 PM
Subject: Re: Us
forward.
Is this what you were going for?
- Original Message - From: "Christian Mittendorf"
<[EMAIL PROTECTED]>
To: "Tapestry users"
Sent: Tuesday, January 31, 2006 4:34 PM
Subject: Re: Using fieldTrackings
Am 01.02.2006 um 01:20 schrieb Jesse Ku
throwing ValidatorException in
rewindFormComponent()). It was pretty straight forward.
Is this what you were going for?
- Original Message -
From: "Christian Mittendorf" <[EMAIL PROTECTED]>
To: "Tapestry users"
Sent: Tuesday, January 31, 2006
Am 01.02.2006 um 01:20 schrieb Jesse Kuhnert:
Hmmm...I know the tapestry workbench demo application has a sample
"ShowErrors" sort of component for this.
The biggest reason I suggested the ValidationDelegate approach is
because
you're guaranteed to get every fields value and error written ou
Am 01.02.2006 um 01:20 schrieb Jesse Kuhnert:
Hmmm...I know the tapestry workbench demo application has a sample
"ShowErrors" sort of component for this.
Ok, I think I'll have to check it.
The biggest reason I suggested the ValidationDelegate approach is
because
you're guaranteed to get eve
Am 01.02.2006 um 01:06 schrieb Jesse Kuhnert:
If you wanted to display error messages next to the fields in
question I
would highly reccomend looking at this (though it uses labels, you can
override whichever method points you want):
http://jakarta.apache.org/tapestry/UsersGuide/
validation.
Hmmm...I know the tapestry workbench demo application has a sample
"ShowErrors" sort of component for this.
The biggest reason I suggested the ValidationDelegate approach is because
you're guaranteed to get every fields value and error written out properly
as everything is passed in as a paramter
Error tracking is working really nice, that is not the problem. My
problem is that not every form field does record its input value to
the trackingFields. Textfields do always record their values, even if
no error occured.
On my page I'm iterating the trackingFields while I'm building up th
If you wanted to display error messages next to the fields in question I
would highly reccomend looking at this (though it uses labels, you can
override whichever method points you want):
http://jakarta.apache.org/tapestry/UsersGuide/validation.html#validation.delegate
On 1/31/06, Christian Mitte
I don't know why checkbox propertySelection aso don't have validator, I
guess they are not that common, but you can validate them in your
submit/form listener and add trackings to the delegate, making the
errors apear on each IFormComponent...
you just call one of the error tracking methods on
16 matches
Mail list logo
