m/-S2--Conversion-validation-issue-tp18576772p22862154.html
Sent from the Struts - User mailing list archive at Nabble.com.
That's my experience too. That's why I wanted to avoid validation
after conversion error on a field.
Is there any interest in adding this functionality? I think that would
be fairly easy to add. If I understood the code correctly, it would be
a matter of extending the DefaultActionValidatorManager
--- On Tue, 7/22/08, Gabriel Belingueres <[EMAIL PROTECTED]> wrote:
> But then again, eliminating the "conversionError"
> interceptor from the stack would prevent conversion
> errors to appear as fieldErrors in the input form,
> but this would force to use the conversion validator
> everywhere a
But then again, eliminating the "conversionError" interceptor from the
stack would prevent conversion errors to appear as fieldErrors in the
input form, but this would force to use the conversion validator
everywhere a non String object is setted by the ParametersInterceptor
to show the error?
Is
> Does this means eliminating the "conversionError" interceptor from the
> default stack?
Yes ;-)
Regards
--
Lukasz
http://www.lenart.org.pl/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
Hi, I'm using Struts 2.1.2:
I have a validation file like this:
El código de validación es requerido
1
El código de validación debe ser un número
positivo
codigoValidacion is an Integer prop
6 matches
Mail list logo