hmm, if i use the validation like this:
void onValidateFromCount(Integer value) throws ValidationException
{
if (value.equals(13)) throw new ValidationException("Thirteen is
an unlucky number.");
}
the Errors-Component of Tapestry displays two errors:
first: org.apache.tapestry5.ValidationException: Thirteen is an unlucky number.
and second: Thirteen is an unlucky number.
is this the desired behavior?
with regards
Sven Homburg
Founder of the Chenille Kit Project
http://chenillekit.codehaus.org
2010/9/8 Sven Homburg <hombu...@googlemail.com>:
> hehe, cool
>
> i cant see the forrest .... there are too many trees in front of
>
> with regards
> Sven Homburg
> Founder of the Chenille Kit Project
> http://chenillekit.codehaus.org
>
>
>
>
>
> 2010/9/8 LLTYK <ll...@mailinator.com>:
>>
>> 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 from the Tapestry Users mailing list archive at Nabble.com.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
