[
https://issues.apache.org/struts/browse/WW-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43382#action_43382
]
Marc-Andre Thibodeau commented on WW-2002:
------------------------------------------
The field that was validated at that time was indeed of type String so we
discovered later on that the RequiredStringValidator was working as
expected. But still, client-side and server-side validation are yielding
different results in this case, which we found confusing.
MA
On Tue, Feb 26, 2008 at 1:31 PM, Kedar Choudhary (JIRA) <[EMAIL PROTECTED]>
> Inconsistent client/server validation using RequiredFieldValidator
> ------------------------------------------------------------------
>
> Key: WW-2002
> URL: https://issues.apache.org/struts/browse/WW-2002
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - CodeBehind
> 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.1.2
>
>
> 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.
