On 8/8/06, Torsten Krah <[EMAIL PROTECTED]> wrote:
How does saveState work - does it call the getter to get the data and then when restoring build the bean from scratch and calling the setter?
Yes, it calls the getter and puts the results into the component tree. On restore, it will restoreState the object. If the object doesn't implement StateHolder, it'll use Serialization. [Un]Serialization uses newInstance() to recreate the bean so no constructors will be called, and the new object != to the old object in the Object.equals() sense of the equality). It then calls the setter with this value.
Is the order relevant - e.g. calling the setWrappedData clears the sorted things - any call previous to this one to set the sort order back from the savedState will be lost in this case - what to do here?
Yes, I think the order is important. You'll probably want to have the saveState for the wrapped data before the saveState for the sort behavior.
