I'm using Wicket 6. As you can see I'm already using new PageProvider(new CustomErrorPage()) 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? -- 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]
