[WICKET-5214] Unrendered component wrongly ignored

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 6.5.0
• Labels: enclosure
• Assignee: Unassigned
• Reporter: Adrian Sándor
• Created: 01/Jun/13 09:27
• Updated: 27/Jan/14 15:03
• Resolved: 18/Jun/13 07:37

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]

Issue Links

• duplicates: WICKET-4874 "Cannot find element with id" error seen in Ajax Debug for child of wicket:enclosure