I agree. I think we can rely on the client to submit all the form values every time. Thus, the submitted value in the state is just going to be constantly overwritten.
On Mon, 21 Feb 2005 18:07:52 +0100 (CET), sean schofield (JIRA) <[EMAIL PROTECTED]> wrote: > [ > http://issues.apache.org/jira/browse/MYFACES-108?page=comments#action_59518 ] > > sean schofield commented on MYFACES-108: > ---------------------------------------- > > I would disagree that submitted value must be stored in the state. I am > relatively new to Faces though so I could be mistaken. > > I agree with you that if there is a validation error, then the incorrect > value needs to be redisplayed. I don't understand, however, why the > submitted value needs to be stored in the state to accomplish this. The > state is really only needed for the Restore View phase. The rendering code > that displays the submitted value instead of the actual value can get the > submitted value from the component itself. After this is done there is no > need to store this bogus value in the state. It has already been sent to the > user and the user can either resubmit the same bogus value or try a new one. > > If you check UIInput in the RI they are not saving the submitted value to > state either. If we are relying on the submitted value to be stored in the > state, that is probably not a good idea. > > > 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 > > -- -Heath Borders-Wing [EMAIL PROTECTED]
