That's a perfect question and an important issue. Indeed there was such a "save descendant states" logic in my original UIData code. As I remember this was one of the more complex parts. States where only to be saved when all children where valid, and so on. Well, this logic has vanished during the refactoring by Mathias Broekelmann.
Mathias, can you please disclose your rationale to drop this?! Thanks, Manfred 2005/11/29, Simon Kitching <[EMAIL PROTECTED]>: > Hi, > > The UIData uses the "flyweight" pattern so that a single set of > component children for a single row are enough to implement a table with > any number of rows. The state for each row is stored in _rowState. > > When a view is serialized, the state for ordinary components is stored. > I presume that the _rowState is also stored at the same time, and for > the same reasons. Among other things I believe this info would be > necessary to re-rended submitted values for input fields if validation > should fail. > > But I just can't see anything in the UIData component that saves the > _rowState. > > Can anyone give me a hint? > > Thanks, > > Simon >
