the current implementation doesn´t work if preservedatamodel=true for nested datatables is set. I will fix this.
Is it working for you now? Regards, Mathias Martin Marinschek schrieb: > upon rethinking: > > is it necessary at all to preserve the dataModel of the inner table - as > soon as the outer table datamodel is saved, automatically the dataModel > of the inner table will be serialized as well, as inner table usually > refer to parts of the datamodel of outer tables, right? > > So if I set preserveDataModel to false in the inner dataTable, still the > outer table will restore its dataModel and everything will be all set. > > regards, > > Martin > > On 8/4/05, *Martin Marinschek* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > hmm, > > I just seem to recall that it worked with the old dataTable, even > with inner tables. > > You are saving the dataModel of the dataTable out to the client if > preserveDataModel is true, right? > > it's just about the dataModel of the inner table? > > I don't have huge tables here, I just want to display several > persons with each one having several contact addresses, and I don't > want to restrict the editing to just one person at a time... > > regards, > > Martin > > > On 8/4/05, *Mathias Broekelmann* < [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Yes that is right (sadly). > > The state of each row is not saved between requests. The spec > doesn´t > say anything about this but IMO implementing it would be easy. > But the > result would be a huge state (depends on rowcount, and nested > components) which wouldn´t be easy to handle if it is saved on > client side. > > What do you think about this? > > Regards, > Mathias > > Martin Marinschek schrieb: >> Hi *, >> >> just a short question, could it be that nested dataTables with >> preserveDataModel=true on both dataTables are not working? The > dataModel >> of my inner table seems to be reset to null at every request... >> >> regards, >> >> Martin > > >
