[ http://issues.apache.org/jira/browse/MYFACES-824?page=comments#action_12357653 ]
Adam Winer commented on MYFACES-824: ------------------------------------ It's not a bug, nor is it being revisited. I'm not aware of many taking issue to this - perhaps you're thinking of the fact that validators are not executed if required is true? submittedValue being set to null means "nothing was submitted" - which is different from "a null value was submitted", or "the empty string was submitted". This is the proper value for submittedValue for a disabled or readonly text field, for instance. This does create some oddities if you want to reflect "the value that was submitted should be null", in which case Renderer.decode() needs to store some non-null value (Boolean.FALSE, etc.), which getConvertedValue() can recognize and change to null. > if submittedValue==null, required==true not checked > --------------------------------------------------- > > Key: MYFACES-824 > URL: http://issues.apache.org/jira/browse/MYFACES-824 > Project: MyFaces > Type: Bug > Components: JSR-127 > Versions: Nightly > Reporter: Dave Brondsema > Priority: Minor > > In UIInput.java, in validate() at line 263 there is "if (submittedValue == > null) return;" > This seems to be incorrect to me. If submittedValue is set to null, then > validate returns without checking to see if required=true. According to the > UIInput spec javadocs " If the component wishes to indicate that no > particular value was submitted, it can either do nothing, or set the > submitted value to null." -- 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
