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

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Implemented
• Affects Version/s: 7.0.0-M5, 6.19.0
• Fix Version/s: 6.20.0, 7.0.0-M6
• Component/s: wicket
• Assignee: Andrea Del Bene
• Reporter: Jon Mann
• Created: 07/Apr/15 17:59
• Updated: 15/Apr/15 08:27
• Resolved: 13/Apr/15 08:27

Description

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.