On 9/24/07, Xavier Hanin <[EMAIL PROTECTED]> wrote: > On 9/25/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > > Gee that looks weird. As far as I know, the only exotic stuff we do > > with serializing is an optimization for page references. But I can't > > see how that might relate to this. > > > > Johan, any ideas? Any chance you could make a test case out of it Xavier? > > > The problem is that without the slightest idea of where it comes from it's > difficult to make a test case. The code is public though, so I have a "large > test case" :-) > But I'm ok to investigate on my own, if you can give me some hints... Maybe > I can switch to another serialization implementation, if I remember well > that's something possible, no?
You could try that (Objects#setObjectStreamFactory(new WicketObjectStreamFactory()) but since we are now using Java's default serialization, I doubt that would make things better. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
