Depends on what wicket version you are using. As for 1.3, the page indeed must be serialized. There is no way around it. The exception shouldn't have been swallowed though. Are you sure it wasn't in your logs?
Prior beta 3, default page store is FilePageStore which serializes page in separate thread, so there is no way to display an error page. But still, the exception should have been in your log. -Matej On 8/28/07, Bart Molenkamp <[EMAIL PROTECTED]> wrote: > > Hi, > > I tried to apply versioning to my pages to support browser back > and forward. This doesn't seem to work when the page can't be > serialized to disk, when going back with the browser's back button > I get PageExpiredExceptions. This is because the serialized page > can't be found (because serialization failed in the first place). > > Serialization failed because not everything on my page implemented > java.io.Serializable (my fault). The serialization throws an > exception, but it is swallowed at > org.apache.wicket.util.lang.Objects, line 1113. > > Why is this exception swallowed? Isn't it a good idea to rethrow it? > It took me a few hours to find out why versioning wasn't working... > > Thanks, > Bart. >
