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?
