You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by bu...@apache.org on 2003/03/12 18:30:28 UTC
DO NOT REPLY [Bug 16548] -
javascript validations all depend on required
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16548>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16548
javascript validations all depend on required
eschnell@nvisia.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|Enhancement |Major
Status|RESOLVED |REOPENED
Priority|Other |Medium
Resolution|FIXED |
Target Milestone|--- |1.1 Family
Version|1.1 Beta 2 |1.1 RC1
------- Additional Comments From eschnell@nvisia.com 2003-03-12 17:30 -------
In 1.1RC1 "required" is still implied for minLength and maxLength such that if
the field is empty it fails both minLength and maxLength.
In version 1.5 (most recent nightly) of FieldChecks.java, Line 885 for minLength
and Line 838 for maxLength should call
"if (!GenericValidator.isBlankOrNull(value)) {"
instead of
"if (value != null) {"
A case could be made (though I disagree with it) that minLength implies
required. It is unquestionably a bug that maxLength implies required.
An optional State abbreviation field could have a minlength of 2 and a maxlength
of two without being required. In RC1 FieldChecks will generate 2 errors if no
value is specified.
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org