That might be a solution: do ValidPropertySelection and ValidCheckbox
record their input values to the ValidationDelegate in any case, even
if no error occured?
Am 01.02.2006 um 01:44 schrieb Daniel Lydiard:
I was actually using the ValidPropertySelection and ValidCheckbox
in my T3 code (http://issues.apache.org/bugzilla/show_bug.cgi?
id=29535) and ported it over to T4. I basically took the existing
T4 source for PropertySelection/Checkbox and added in the code to
work with ValidationDelegate (by 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" <tapestry-user@jakarta.apache.org>
Sent: Tuesday, January 31, 2006 4:34 PM
Subject: Re: Using fieldTrackings
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 every fields value and error written out
properly
as everything is passed in as a paramter to you.
Are you sure that this approach is also working with
PropertySelection or
Checkboxes?
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
