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.validate() method to check first if the field is in the conversionError map (in that case it should skip validation of that field). 2008/7/22 Dave Newton <[EMAIL PROTECTED]>: > --- 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 String object is setted by the >> ParametersInterceptor to show the error? > > In my experience most conversion errors also result in validation errors, at > least for simple cases. > >> Is there any way to configure S2 so that when a conversion >> error happens on a field, it does NOT try to validate later >> that specific field in the Validator interceptor? > > Not at the moment, AFAIK. > > Dave > > > --------------------------------------------------------------------- > 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]
