Re: [S2] Conversion validation issue

I've had exactly the same problem and ended up doing the same thing you suggested, over-riding the validate() method and checking for existing field (data conversion) errors and skipping validation if (field) errors were found. -- View this message in context:

Re: [S2] Conversion validation issue

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

Re: [S2] Conversion validation issue

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

Re: [S2] Conversion validation issue

--- 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 non

Re: [S2] Conversion validation issue

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