[ http://issues.apache.org/jira/browse/MYFACES-1467?page=comments#action_12443127 ] Adam Winer commented on MYFACES-1467: -------------------------------------
It cannot be fixed in UIInput "once for all", because the spec describes how UIInput must behave. There are no options other than spec compliance. For the specific choice for cross-field validation, adding a component as the last one is not a good strategy, since this will break in future partial lifecycle executions (e.g., DynaFaces). Also, don't know why you'd want to make such a component a UIInput, since it really doesn't have a value of its own. > 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.1.5-SNAPSHOT, 1.2.0-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
