The exception is not propagated because the request is already dispatched to the user and nothing can be shown. You *really* need to take a look at the log files during development.
Logging the exception is the best effort we can do. Martijn 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. > -- Wicket joins the Apache Software Foundation as Apache Wicket Apache Wicket 1.3.0-beta2 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta2/
