[ http://issues.apache.org/jira/browse/MYFACES-1467?page=comments#action_12442373 ] Matthias Weßendorf commented on MYFACES-1467: ---------------------------------------------
I pretty much think that the single value validation is a good thing. JSF is a spec not a product. so myfaces or ri can (not must) handle this different. At least it (single v. valid.) protcets you from bad bad hooks of the frameworks itself. at least you need to write a *framework* on top of faces for that yourself. (which only you (or a community) is in charge of it) > Validation doesn't run for required fields if submitted value is null > --------------------------------------------------------------------- > > Key: MYFACES-1467 > URL: http://issues.apache.org/jira/browse/MYFACES-1467 > Project: MyFaces Core > Issue Type: Bug > Components: General > Affects Versions: 1.2.0-SNAPSHOT, 1.1.5-SNAPSHOT > Reporter: David Chandler > Assigned To: Matthias Weßendorf > Attachments: patch.txt > > > A component with a required value will not fail validation as expected if the > submitted value is null. This issue is not seen normally because browsers > send the value for an empty text field as an empty string. That is, the POST > data for an empty field1 will contain the field name but no value, like > field1=&field2=something. However, if you use a man-in-the-middle proxy such > as Paros to remove "fieldname=" from the POST data, the submitted value will > be null. UIInput.validate() skips validation for null submitted values, but > since requiredness is also part of validation, the requiredness check gets > skipped, too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
