[jira] [Resolved] (WICKET-5389) Allow continued processing with WicketTester after exception is thrown

["Sven Meier (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-5389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sven Meier resolved WICKET-5389.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 7.0.0

Next request is now prepared in a finally block.

I didn't commit the change for 6.x since it implies a slight change:
After an exception is thrown, no longer #getRequest() is used to access the failed request, but #getLastRequest() as in all other cases where no exception occurs.

> Allow continued processing with WicketTester after exception is thrown
> ----------------------------------------------------------------------
>
>                 Key: WICKET-5389
>                 URL: https://issues.apache.org/jira/browse/WICKET-5389
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 7.0.0, 6.11.0
>            Reporter: Sven Meier
>            Assignee: Sven Meier
>            Priority: Minor
>             Fix For: 7.0.0
>
>
> When exposing an exception while processing, WicketTester is left in an inconsistent state. Since #setupNextRequestCycle() is not called, no additional processing is possible afterwards:
>    org.apache.wicket.WicketRuntimeException: No RequestCycle is currently set!
> For tests expecting WicketTester#process() to fail, it would be nice to be able to continue processing with the same tester instance afterwards.



--
This message was sent by Atlassian JIRA
(v6.1#6144)