On Tue, Nov 5, 2013 at 8:27 PM, dgn <[email protected]> wrote:
> Ah, now I read more closely. My apologies... > > Yes, using new PageProvider(new CustomErrorPage.class) results in the > desired behavior where AbstractRequestCycleListener#onException() is only > called once. > > I'm curious why using an explicit constructor of a class as a parameter of > "new PageProvider()" causes multiple calls to onException() where the later > calls contain a PageExpiredException. > > Ideally I'd like to be able to capture any message contained within the > original exception that was being trapped and passing it to the > CustomErrorPage. Is there another means of capturing this exception? > > Try with: Session.get().bind() before returning the error page *instance*. > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Cannot-get-to-desired-error-page-on-handling-RuntimeException-in-AbstractRequestCycleListener-onExce-tp4662078p4662145.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] > >
