preserveRowState will not store the datamodel it only stores the rowstate which is held/created during the livecycle and will not be a part of the state between the requests.
2005/9/28, Martin Marinschek <[EMAIL PROTECTED]>: > With preserveRowState, you mean something like preserveDataModel, but > storing it until the end of the lifecycle? > > regards, > > Martin > > On 9/28/05, Mathias Brökelmann <[EMAIL PROTECTED]> wrote: > > input components inside a datatable depends on a datamodel. If > > processing in validation and update model phases succeeds without an > > error we have to get a new value of the datamodel. This new datamodel > > can be changed in every aspect. It could have the same content but in > > different order, can have more or less rows with different data. The > > datatable is not able to determine how its value has been changed. If > > the order of the rows changed and we do not discard the row state > > (including the submitted value) you would get unpredictable results > > and the submitted values are displaced. > > So this is not only an issue with the spec its also an issue with the > > implementation. > > > > The only thing we could do is to create a new attribute for > > t:datatable like preserveRowState which could allow you to define if > > you don´t want to discard the rowstate in encodeBegin(..) method. You > > can contribute a patch for this. > > > > 2005/9/27, Peltier, Tara <[EMAIL PROTECTED]>: > > > Mathias, > > > > > > Why do you think that an inputText component inside a dataTable behaves so > > > differently from an inputText component that is not inside a dataTable? > > > > > > This seems quite bizarre to me. > > > > > > Regards, > > > --Tara > > > > > > -----Original Message----- > > > From: Mathias Brökelmann [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, September 27, 2005 2:19 PM > > > To: MyFaces Discussion > > > Subject: Re: DataTable with Immediate Buttons Lose Submitted Values In > > > 1.1.0 > > > > > > I´ve closed this bug since it is documented in the spec that it should > > > be as we have implemented it. > > > > > > See http://issues.apache.org/jira/browse/MYFACES-632 > > > > > > 2005/9/27, [EMAIL PROTECTED] > > > <[EMAIL PROTECTED]>: > > > > > > > > I can confirm this wrong behaviour. But a clone of MYFACES-277 is > > > > somehow > > > > missleading. On the contrary the desired behaviour is the opposite of > > > > it. > > > > Seems like a UIData bug, that was introduced at this time. > > > > > > > > > -- > > > Mathias > > > > > > > > > > > > -- > > Mathias > > > > > -- > > http://www.irian.at > Your JSF powerhouse - > JSF Trainings in English and German > -- Mathias
