You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2010/08/27 20:38:53 UTC

[jira] Commented: (WICKET-3022) All exceptions are handled by RequestCycle and no longer "visible" to WicketTester

    [ https://issues.apache.org/jira/browse/WICKET-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903520#action_12903520 ] 

Igor Vaynberg commented on WICKET-3022:
---------------------------------------

i thought i already had support for this baked in there, i think tester installed its own exception mapper....dont remember off the top of my head but it used to work

> All exceptions are handled by RequestCycle and no longer "visible" to WicketTester
> ----------------------------------------------------------------------------------
>
>                 Key: WICKET-3022
>                 URL: https://issues.apache.org/jira/browse/WICKET-3022
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5-M1
>            Reporter: Juergen Donnerstag
>            Assignee: Juergen Donnerstag
>
> Exceptions during render will no longer be detected by WicketTester, since RequestCycle handles them all. Which is ok for normal processing, but bad for WicketTester. We somehow need to make WicketTester aware of thrown exceptions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.