[ http://issues.apache.org/jira/browse/MYFACES-108?page=comments#action_59492 ] Manfred Geiler commented on MYFACES-108: ----------------------------------------
Submitted value MUST be saved in state. Whenever a component has a non-valid value the submitted value must be saved in state to be restored for redisplaying. Otherwise the value would be lost, because the bound model bean does not know anything of the new value yet. > UIInput should not store submitted value in the state > ----------------------------------------------------- > > Key: MYFACES-108 > URL: http://issues.apache.org/jira/browse/MYFACES-108 > Project: MyFaces > Type: Improvement > Versions: 1.0.7 beta, 1.0.8 beta > Reporter: sean schofield > Priority: Trivial > > Submitted value really shouldn't be stored in the state. At a minimum it is > confusing and results in extra bandwith with client-side state saving. Heath > points out that in most cases the value being "stored" will probably be null. > That being said, if the code is totally unecessary we ought to consider > removing it. I will leave this issue open for a while to make sure nobody > has any issues with fixing it. This will affect a lot of components so I > want to be sure this is the right thing to do. I will provide a patch > eventually. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
