Hi Werner,
yes it should fix this issue. You can use sortheader (immediate
attribute must be set to false for sortheader), inputfields, nested
uidatas and datascrollers with the patch for 305 and the new uidata
implementation.
Mathias
Werner Punz schrieb:
Just a question, does the new ui data also solve the problem
of losing the scroller/ data table states if you traverse pages
over a faces-config defined pageflow into the same page?
I stumbled over that problem and discussed it in the user
list last week. (x:savestate did not help in this case either)
Werner
Grant Smith wrote:
I took the liberty of assigning MYFACES-305 to Sean, as he applied the
first patch (and it's about TIME he did some work... yeah, right).
Mathias, please upload this new patch to the JIRA too. I will help out
with the testing once it's all in SVN. We use UIData extensively, and
if there are bugs to be found, my convoluted apps are bound to bring
them to the surface :)
Broekelmann, Mathias wrote:
Hi,
I love to work under pressure which is what I do in every "normal"
project at these times :)
Ok lets see what the new implementation fixes or not. I´ve done a lot
of tests but I`m sure that´s not enough. So it´s up to you to to test
it in your applications. Please take a look at the bug 305 (and his
fix :-)) if you try to test the datatable with a datascroller component.
I´ve also removed the code for the special handling of embedded
UIData´s. It is now handled by the saveState and restoreState methods
which are used now to save the state for each row while iterating the
datamodel. I´ve added some code to prevent that the state is also
saved into the client or server states between the requests.
Happy testing!
Mathias
