You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Noel Hernández (JIRA)" <ji...@apache.org> on 2008/12/25 11:27:37 UTC

[jira] Commented: (WW-2255) Field validators should be skipped if there is a conversion error

    [ https://issues.apache.org/struts/browse/WW-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45380#action_45380 ] 

Noel Hernández commented on WW-2255:
------------------------------------

I think that you can't use struts in a real world project without resolve this issue. 
I'm wondering if it works the same in XWork.
I'm using the workaround of Tom Scheneider, thanks Tom, but right now my team mates has loose the confidence in the struts2 project looking at new releases without this issue being solved.

> Field validators should be skipped if there is a conversion error
> -----------------------------------------------------------------
>
>                 Key: WW-2255
>                 URL: https://issues.apache.org/struts/browse/WW-2255
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: XML Validators
>            Reporter: Adam Crume
>             Fix For: 2.2.x
>
>         Attachments: ConversionErrorInterceptor2.java
>
>
> If there is an error converting a field, the validators for that field should be skipped.  For example, let's say I have an action with an "age" field declared as an Integer, and the field is required.  If the user enters "one", the user will see two errors: one from the conversion process, and one from the required validator (since the field was never assigned).
> In general, a conversion error should short-circuit all validators for that field, since validators depend on the field being set, which never happens if there was a conversion error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.