The Exception is only logged (as ERROR) if something is not serializable, so it will only complain in your logfile. See Objects.objectToByteArray() method.
I don't think page serialization is done in a seperate Thread though. I couldn't find this in the code. But please correct me if I am wrong. Lars On Tue, Apr 1, 2008 at 9:09 PM, Matej Knopp <[EMAIL PROTECTED]> wrote: > Are you sure your attributes were not transient? There's no way wicket > would skip it without an error. ObjectOutputStream should certainly > complain and we do log the serialization exception. > > -Matej > > On Tue, Apr 1, 2008 at 8:31 PM, James Carman <[EMAIL PROTECTED]> > wrote: > > On Tue, Apr 1, 2008 at 2:17 PM, Antoine Angénieux > > <[EMAIL PROTECTED]> wrote: > > > I just fixed a bug in one of my wicket apps that was linked to page > > > versions disk serialization... > > > > > > I had an object that did not implement Serializable that was deep > down > > > in the object instances hierarchy (like page -> some object -> ... > --> > > > non serializable object). > > > > > > Wicket never complained about any serialization problem, but off > course, > > > when my page was restored from the disk store, it was deserialized > > > without any of its attributes (thus causing some null pointer > exception > > > in my code). > > > > > > I was wondering if that was the expected behavior, and if not, if it > was > > > the DiskPageStore that was to blame of the plain old java > serialization > > > mechanism... > > > > > > What do you guys think ? > > > > I believe the disk store stuff is done in another thread. Are you > > sure it didn't print off the error message in your logs and you didn't > > notice it? > > > > > > -- > Resizable and reorderable grid components. > http://www.inmethod.com >
