Hi,
On Mon, Nov 4, 2013 at 4:00 PM, dgn <[email protected]> wrote: > I'm using Wicket 6. > > As you can see I'm already using new PageProvider(new CustomErrorPage()) > Sven suggested you to try with the other constructor of PageProvider - the one that access a Class. > when I get the runtime exception I'm targeting. > > What I'm wondering and perhaps don't understand fully is the Wicket request > lifecycle. What is causing the callback to onException() multiple times? > The > first time I'm unwrapping the desired exception but subsequently it's a > PageExpiredException. I'm pretty sure my CustomErrorPage is stateless so > don't understand why the additional exceptions. Any suggestions? > If you are able to reproduce the problem in a mini application then create a ticket in JIRA and attach it. We will take a look what goes wrong. > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Cannot-get-to-desired-error-page-on-handling-RuntimeException-in-AbstractRequestCycleListener-onExce-tp4662078p4662109.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
