https://issues.apache.org/jira/browse/WICKET-4269

-igor

On Mon, Nov 28, 2011 at 6:47 AM, peakmop <peak...@yahoo.com> wrote:
> 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 there something that can be done to prevent an
> exception and receive a boolean response from the call, or if the exception
> is expected (which makes the boolean logic irrelevant), how to handle it
> most appropriately so the next request handler is executed (which is what
> replaceAllRequestHandlers() is intended to perform in the first place)?
>
>
>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/Handling-ReplaceHandlerException-on-continueToOriginalDestination-in-wicket-1-5-tp4101981p4115437.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to