[ http://issues.apache.org/jira/browse/MYFACES-1467?page=comments#action_12442359 ] Martin Marinschek commented on MYFACES-1467: --------------------------------------------
Hi David, Cagatay, Matthias, this bug is indeed a problem in the sourcebase. On a sidenote - I believe that it is bad to skip validation at all if the value of a field is null. What if you want to have a field which is only required if a defined other field has a certain value? You can't just set the required-attribute (you can also not value-bind the required attribute properly, cause you don't necessarily have the converted and validated value of the other field in your backing bean model), and will need a special validator. Fact is that this special validator will never be executed, if the value is null, so effectively, you can't do the validation. I believe we should change this in the next version of the spec. regards, Martin > 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
