You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@struts.apache.org by "James Holmes (JIRA)" <ji...@apache.org> on 2007/08/17 15:22:34 UTC

[jira] Updated: (WW-2002) Inconsistent client/server validation using RequiredFieldValidator

     [ https://issues.apache.org/struts/browse/WW-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Holmes updated WW-2002:
-----------------------------

    Affects Version/s: 2.0.9
        Fix Version/s:     (was: Future)
                       2.0.11

> Inconsistent client/server validation using RequiredFieldValidator
> ------------------------------------------------------------------
>
>                 Key: WW-2002
>                 URL: https://issues.apache.org/struts/browse/WW-2002
>             Project: Struts 2
>          Issue Type: Bug
>    Affects Versions: 2.0.8, 2.0.9
>         Environment: Windows 2000, Tomcat 5.5.23, java 1.6.0_01
>            Reporter: Marc-André Thibodeau
>             Fix For: 2.0.11
>
>
> We noticed different behaviors between client-side and server-side validations using a RequiredFieldValidator annotation.  Using this annotation, an empty field is considered invalid when validated on the client-side, while it is accepted by the server-side validation (when javascript is not supported). It does not downgrade gracefully.

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