Yes it is ugly, but there is no other way to get the page serializing correct, this is the fix for the stackoverflow problem that people where reporting.
On 5/6/08, Martin Grigorov <[EMAIL PROTECTED]> wrote: > Hi, > > Browsing the Wicket code I saw that o.a.w.Component has readObject and > writeObject methods which in their current implementation actually do > some specific serialization if the current instance is a Page. > Is there any specific reason to put this code in Component but in Page ? > Currently it breaks the OO design - the parent knows about the type of > its children and even more it knows about children's specifics - > read/writePageObject(). > > Regards > Martin > >
