> Today I pulled wicket-1.3-SNAPSHOT from svn and built it. When I disable
> the tests, the build is OK, but with tests enabled many other errors
> showed up than the one I asked about in my original post. (I don't think
> I have to post them here, as anyone should be able to reproduce this?!)
Sho
Hello Eelco,
Op vrijdag 25-05-2007 om 23:12 uur [tijdzone +0200], schreef Eelco
Hillenius:
> in your application's init method
"my application" doesn't exist yet, I'm just trying to build the
examples.
> (or update to the latest Wicket snapshot)? If the problem stays, it
> should give you a cl
Reinout, could you please try putting:
org.apache.wicket.util.lang.Objects.setObjectStreamFactory(new
IObjectStreamFactory.DefaultObjectStreamFactory())
in your application's init method (or update to the latest Wicket snapshot)?
If the problem stays, it should give you a clearer message what is
It looks like your page, or a model or component attached to that page
holds a reference to an object that cannot be serialized. That's a
no-no. Once a request has been processed, the pages are serialized and
stored in a cache in case the user needs to access them again via back
button.
On Fri,
