To follow up, and to put this issue at rest, here's the explanation (thanks to the wicket authentication examples): The ReplaceHandlerException will get thrown if there is an active request handler on the stack to stop its execution and start executing the new request handler (usually RedirectRequestHandler) if the original request was for some bookmarkable page. The exception eventually will get intercepted in the request handler code and the new request handler will get executed, and the requested page will eventually be rendered. Since before WICKET-4269 addressed the return values of continueToOriginalDestination(), that method return values were used to determine whether a redirect to the default (usually home page) or a redirect to the requested page is to take place. I was catching an Exception in the login page which also intercepted the ReplaceHandlerException which prevented the replacement request handler from being successfully executed down the road. I didn't realize this until I attached a debugger to the authentication examples. Developers can correct me if I'm off in my explanation here.
-Martin- -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Handling-ReplaceHandlerException-on-continueToOriginalDestination-in-wicket-1-5-tp4101981p4123670.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]
