[
https://issues.apache.org/jira/browse/WICKET-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15439205#comment-15439205
]
ASF subversion and git services commented on WICKET-6233:
---------------------------------------------------------
Commit f33159644a04c664d6cca106473fd1df82261b08 in wicket's branch
refs/heads/master from [~mgrigorov]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=f331596 ]
WICKET-6233 Add component info in the error messages related to
WicketTester#assertComponentOnAjaxResponse()
> Add component info in the error messages related to
> WicketTester#assertComponentOnAjaxResponse()
> -------------------------------------------------------------------------------------------------
>
> Key: WICKET-6233
> URL: https://issues.apache.org/jira/browse/WICKET-6233
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 6.24.0
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Priority: Minor
> Fix For: 8.0.0-M2, 6.25.0, 7.5.0
>
>
> Error messages from
> org.apache.wicket.util.tester.WicketTester#assertComponentOnAjaxResponse(java.lang.String)
> are not very helpful at the moment because they don't mention the component
> id/path that is not found in the Ajax response.
> One has to use the stacktrace to figure out which component is failing.
> This could be improved by adding the component info
> (Component#toString(false)) in the error messages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
