[
https://issues.apache.org/jira/browse/WICKET-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487319#comment-14487319
]
Andrea Del Bene commented on WICKET-5875:
-----------------------------------------
The problem with renderComponent is that it removes the target component from
its original hierarchy and puts it in a dummy page to initialize the component
and render it.
I've changed the code in order to check if the target component has already a
parent and if so, the dummy page is not used.
> ComponentRenderer.renderComponent() unexpectedly produces a
> WicketRuntimeException when called with a nested Component which contains a
> nested wicket:message
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-5875
> URL: https://issues.apache.org/jira/browse/WICKET-5875
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.19.0
> Reporter: Jon Mann
> Assignee: Andrea Del Bene
> Attachments: 5875.zip
>
>
> ComponentRenderer.renderComponent() unexpectedly produces a
> WicketRuntimeException when called with a nested Component which contains a
> nested "wicket:message".
> The nested Component works OK in production.
> But our tests fail unexpectedly with a WicketRuntimeException when trying to
> obtain the HTML output from the nested component.
> The WicketRuntimeException is suppressed by
> getResourceSettings().setThrowExceptionOnMissingResource(false) but then
> renderComponent() does not produce the expected HTML.
> See the attached test case against Wicket version 6.19:
> SomeComponentTest.testBasic() PASSES
> SomeComponentTest.testRenderPageToHtml() PASSES
> SomeComponentTest.testRenderSomeComponentToHtml() PASSES
> SomeComponentTest.testRenderLinkToHtml() FAILS unexpectedly
> Hopefully this makes sense.
> Thanks to the Wicket team for a great product.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
