[ http://issues.apache.org/jira/browse/MYFACES-815?page=comments#action_12357521 ]
Hlias Mpalasis commented on MYFACES-815: ---------------------------------------- Oops, I discovered something controversial. It seems that the error is not caused by bug in inputCalendar implementation. The property binding for updating the model with the value entered (or null) in inputCalendar was throwing a NullPointerException exception that was never reported neither in the server's stdout nor in browser as an error page. The reason might be that the property binding set method was declared to throw a FacesException but the exception actually produced was a NullPointerException. I do not know how this is processed by MyFaces JSF core but I suspect that this is what actually happened. I fixed the bug and the behavior disappeared. I therefore not consider this a bug issue anymore but I prefer not to close it yet. Please close it, if you also think this issue is not related to any bugs. > t:inputCalendar "Required" not functioning correctly > ---------------------------------------------------- > > Key: MYFACES-815 > URL: http://issues.apache.org/jira/browse/MYFACES-815 > Project: MyFaces > Type: Bug > Components: Tomahawk > Versions: 1.1.1 > Environment: Windows 2000, Apache 5.5 > Reporter: Hlias Mpalasis > > when "Required" property is set to "false" t:inputCalendar is expected to > accept nulls > Instead it prevents JSF life cycle from entering "Invoke Application" phase. > As a result, applicaitons cannot continue unless a value is entered in > "inputCalendar" field. > I placed a custom phase monitor and discovered that JSF goes through the > following phases in the order specified. > RESTORE_VIEW, APPLY_REQUEST_VALUES, PROCESS_VALIDATIONS, UPDATE_MODEL_VALUES, > RENDER_RESPONSE. Notice that INVOKE_APPLICATION phase is skipped. > I have also observed that when "inputCalendar" is left empty, the model is > updated correctly in UPDATE_MODEL_VALUES phase with a null value but > INVOKE_APPLICATION phase is skipped. > I believe this is abnormal because the "inputCalendar" "Required" property is > set to false. It shouldn't mind about the null. Besides the model is updated > correctly. -- 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
