dont really understand what you mean... continueToOriginalDestination() does alway sthrow the replacehandler exception. this is how that method works...
why is it a problem/why are you trying to deal with the new handler? -igor On Wed, Nov 23, 2011 at 2:57 PM, peakmop <[email protected]> wrote: > 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() ) > { > setResponsePage( getApplication().getHomePage() ); > } > > return; > > The call to continueToOriginalDestination always throws > ReplaceHandlerException and never gets to the 'return' part because it seems > that there is still an active RequestHandler in the RequestHandlerStack. > Do I need to explicitly handle this exception and detach() the current > RequestHandler to let the next scheduled handler execute (and redirect to > the bookmarkable page request), or do I prevent the exception from occuring > somehow (since there wasn't one thrown in wicket 1.4.x)? > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Handling-ReplaceHandlerException-on-continueToOriginalDestination-in-wicket-1-5-tp4101981p4101981.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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
