[
https://issues.apache.org/jira/browse/WICKET-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122351#comment-13122351
]
Andrea Del Bene commented on WICKET-4112:
-----------------------------------------
Well, we could expand method 'startComponentInPage( component, pageMarkup)'
adding a string parameter with the start component path. This parameter can be
saved and used instead of 'startComponent'. Method 'startPanel' will pass panel
id as start component path, while method 'startComponentInPage' will pass a
null.
See provided patch (I didn't tested yet!).
> WicketTester#startComponentInPage and WicketTester#assertModelValue have
> inconsistent behavior.
> -----------------------------------------------------------------------------------------------
>
> Key: WICKET-4112
> URL: https://issues.apache.org/jira/browse/WICKET-4112
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.0, 1.5.1
> Reporter: Martin Dilger
> Attachments:
> 0001-WICKET-4122-WicketTester-uses-absolute-Path-to-refer.patch, wicket.zip
>
>
> I try the following (in Pseudocode):
> tester = new WicketTester();
> tester.startComponentInPage(new Label("test","hello");
> tester.assertModelValue("test","hello"); --> throws
> java.lang.IllegalArgumentException: Component is not a container and so does
> not contain the path test.
> Funny as it is, to make this work, you have to do the following assertion:
> tester.assertModelValue("", "hello");
> The error lies in
> public Component getComponentFromLastRenderedPage(String path,
> final boolean wantVisibleInHierarchy)
> in Line: path = startComponent.getId() + ":" + path;
> I will provide a patch this evening.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
