Re: Handling ReplaceHandlerException on continueToOriginalDestination in wicket 1.5

2011-11-30 Thread peakmop
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

Re: Handling ReplaceHandlerException on continueToOriginalDestination in wicket 1.5

2011-11-28 Thread peakmop
Tor Iver is correct, in 1.4.x the call to continueToOriginalDestination didn't throw an exception but rather a boolean result. While in 1.5.x it still returns a boolean result, but it does so if replaceAllRequestHandlers() call returns without throwing an exception. My question is twofold: is

Handling ReplaceHandlerException on continueToOriginalDestination in wicket 1.5

2011-11-23 Thread peakmop
In MyAuthorizationStrategy that implements IAuthorizationStrategy I throw RestartResponseAtInterceptPageException( LoginPage.class ) if the user is not logged in and requests a bookmarkable page. In the LoginPage onSubmit() the call is made: if ( !continueToOriginalDestination() ) {