You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Adrian Sandor (JIRA)" <ji...@apache.org> on 2013/06/06 09:32:25 UTC
[jira] [Updated] (WICKET-5214) Unrendered component wrongly ignored
[ https://issues.apache.org/jira/browse/WICKET-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrian Sandor updated WICKET-5214:
----------------------------------
Description:
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").setVisible(false));
}
}
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]
was:
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]
> 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").setVisible(false));
> }
> }
> 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