[
https://issues.apache.org/jira/browse/WICKET-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676267#comment-13676267
]
Cedric Gatay commented on WICKET-5214:
--------------------------------------
This is the way setVisible works, it does not check the rendering of an
invisible component. I won't do such a change without the agreement of the team
to do so (as it may break many existing applications and slow things down). The
only update I would propose could be doing this kind of checks only in
development mode.
> Unrendered component wrongly ignored
> ------------------------------------
>
> Key: WICKET-5214
> URL: https://issues.apache.org/jira/browse/WICKET-5214
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 6.5.0
> Reporter: Adrian Sandor
>
> When a page has a hidden enclosure, unrelated components that were not
> rendered are silently ignored (with only a debug message). Example:
> public class HomePage extends WebPage {
> public HomePage() {
> add(new Label("foo", "bar"));
> add(new WebMarkupContainer("baz"));
> }
> }
> Homepage.html:
> Hello <wicket:enclosure><div wicket:id="baz"></div></wicket:enclosure>
> Result: the page shows "Hello".
> If you remove ".setVisible(false)", then...
> Unexpected RuntimeException
> Last cause: The component(s) below failed to render. Possible reasons could
> be that: 1) you have added a component in code but forgot to reference it in
> the markup (thus the component will never be rendered), 2) if your components
> were added in a parent container then make sure the markup for the child
> container includes them in <wicket:extend>.
> 1. [Component id = foo]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
