[
https://issues.apache.org/jira/browse/WICKET-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903569#action_12903569
]
Igor Vaynberg commented on WICKET-3022:
---------------------------------------
we can probably just move the exception loop handling into the exceptionmapper
itself. it sucks because then users have to implement it in their own mappers,
but oh well. maybe what we can do is make it a decorator and decorate the
default with it, that way users can easily do that as well.
> 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.
