You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Jon Mann (JIRA)" <ji...@apache.org> on 2015/04/07 20:00:13 UTC

[jira] [Created] (WICKET-5875) ComponentRenderer.renderComponent() unexpectedly produces a WicketRuntimeException when called with a nested Component which contains a nested wicket:message

Jon Mann created WICKET-5875:
--------------------------------

             Summary: 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



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)