You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Sven Meier (JIRA)" <ji...@apache.org> on 2013/10/17 13:50:42 UTC

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

Sven Meier created WICKET-5389:
----------------------------------

             Summary: 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: 6.11.0, 7.0.0
            Reporter: Sven Meier
            Assignee: Sven Meier
            Priority: Minor


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)