"jsonValidationWorkflowStack" includes "basicStack" which includes
"conversionError" interceptor...

An unintended consequence is that conversion error messages cannot be
customized because ConversionErrorInteceptor runs before
ValidationInterceptor and, thus, will automatically report the field
conversion errors.

Do we really want that for default behavior? The error message is techy and
cryptic to the end user. I don't think we should provide the
"conversionError" in the basicStack. People need to report that themselves
with validation errors.

Cheers,
Paul

Reply via email to