[
https://issues.apache.org/jira/browse/WICKET-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611892#action_12611892
]
Timo Rantalaiho commented on WICKET-1737:
-----------------------------------------
Thanks for reporting, this sounds like a problem that impedes your unit testing
a lot when using a custom markup location.
Would it be possible for you to provide a quickstart with a WicketTester test
failing because of this?
Or better yet a patch against Wicket code that provides a failing unit test.
Meanwhile, in jdave-wicket there is an example of starting components with
markup provided in a String
http://svn.laughingpanda.org/svn/jdave/trunk/jdave-wicket/src/java/jdave/wicket/ComponentSpecification.java
You might be able to do something similar to work around this issue, although
it might involve too much code.
> wicketTester does not find HTML mark-up if custom location is used.
> -------------------------------------------------------------------
>
> Key: WICKET-1737
> URL: https://issues.apache.org/jira/browse/WICKET-1737
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.4
> Reporter: Karsten Efker
> Priority: Minor
>
> If a custom HTML mark-up location is used as described in the ApacheWicket
> Wiki the wicketTester does not find mark-up to render pages.
> refer to:
> http://cwiki.apache.org/WICKET/control-where-html-files-are-loaded-from.html#ControlwhereHTMLfilesareloadedfrom-InWicket1.3
> Nevertheless running the application with ApacheTomcat 6.0.16 everything
> renders fine.
> Remark:
> wicketTester has been instanciated using custom test application extended
> from the application used, overriding newSession for different purpose.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
