You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Marc-André Thibodeau (JIRA)" <ji...@apache.org> on 2007/06/19 17:06:26 UTC
[jira] Created: (WW-2002) Inconsistent client/server validation
using RequiredFieldValidator
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
Environment: Windows 2000, Tomcat 5.5.23, java 1.6.0_01
Reporter: Marc-André Thibodeau
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.
[jira] Commented: (WW-2002) Inconsistent client/server validation
using RequiredFieldValidator
Posted by "Marc-Andre Thibodeau (JIRA)" <ji...@apache.org>.
[ 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) <ji...@apache.org>
> 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.
[jira] Updated: (WW-2002) Inconsistent client/server validation
using RequiredFieldValidator
Posted by "Ted Husted (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Husted updated WW-2002:
---------------------------
Fix Version/s: Future
Setting Fix Version to "future" for issues without a set fix version.
> 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
> Environment: Windows 2000, Tomcat 5.5.23, java 1.6.0_01
> Reporter: Marc-André Thibodeau
> Fix For: Future
>
>
> 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.
[jira] Updated: (WW-2002) Inconsistent client/server validation
using RequiredFieldValidator
Posted by "Kedar Choudhary (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kedar Choudhary updated WW-2002:
--------------------------------
What is the type of field being validated?
If it is String, then RequiredStringValidator should be used rather than RequiredFieldValidator.
> 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.
[jira] Updated: (WW-2002) Inconsistent client/server validation
using RequiredFieldValidator
Posted by "James Holmes (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (WW-2002) Inconsistent client/server validation
using RequiredFieldValidator
Posted by "Musachy Barroso (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Musachy Barroso resolved WW-2002.
---------------------------------
Resolution: Not A Problem
> 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: XML Validators
> 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.3
>
>
> 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.
[jira] Updated: (WW-2002) Inconsistent client/server validation
using RequiredFieldValidator
Posted by "James Holmes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Holmes updated WW-2002:
-----------------------------
Fix Version/s: (was: 2.0.11)
2.0.12
> 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.12
>
>
> 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.
[jira] Commented: (WW-2002) Inconsistent client/server validation
using RequiredFieldValidator
Posted by "Musachy Barroso (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43939#action_43939 ]
Musachy Barroso commented on WW-2002:
-------------------------------------
That distinction cannot be done in javascript. In javascript, even if a field has no value, its value is "", instead of null (like in java). That's why you need to use "requiredstring" as it will check for the string size.
> 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: XML Validators
> 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.3
>
>
> 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.
[jira] Updated: (WW-2002) Inconsistent client/server validation
using RequiredFieldValidator
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Don Brown updated WW-2002:
--------------------------
Component/s: (was: Plugin - CodeBehind)
XML Validators
> 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: XML Validators
> 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.