I've just upgraded from rc1 to 1.3.1 and serveral pages throw RTEs
(org.apache.wicket.WicketRuntimeException: The component(s) below failed to
render.) on rendering. I found out the exception ocurrs whenever a nested
component in a wicket:enclosure tag within a wicket:extend tags is
addressed, better show you some markup:
<wicket:extend>
<wicket:enclosure child="foo:bar">
<div wicket:id="foo">
<div wicket:id="bar">foobar</div>
</div>
</wicket:enclosure>
</wicket:extend>
and here's the code:
public class BlaPage extends HomePage {
public BlaPage() {
final WebMarkupContainer foo = new WebMarkupContainer("foo");
final Label bar = new Label("bar", "bazqux");
// that one doesn't matter
bar.setVisible(false);
foo.add(bar);
add(foo);
}
}
It works, however, when used outside a <wicket:extend> or when it just
affects the first component (child="foo") ... ah yes and it worked in wicket
rc1 (don't know if it worked in rc2 or 1.3.0).
my question: is "foo:bar" supposed to work, was it considered as feature of
the enclosure tag or did it just work coincidentally until rc1 and should
actually be done in a different way?
or should I just raise a JIRA issue? :-)
-----
Michael Sparer
http://talk-on-tech.blogspot.com
--
View this message in context:
http://www.nabble.com/enclosures-on-nested-components-within-wicket%3Aextends-tp15330837p15330837.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
