Hi all,
consider the following markup:
<wicket:enclosure child="label1">
<span wicket:id="label1"></span>
<wicket:enclosure child="label2">
<span wicket:id="label2"></span>
</wicket:enclosure>
</wicket:enclosure>
In Wicket 1.3.0-final I get an Unexpected RuntimeException (WicketMessage:
Expected close tag for <wicket:enclosure child="label1">) when the component
with id "label1" has its visibility set to false. In Wicket 1.3.0-rc2
everything worked fine.
Was this behavior intended when releasing 1.3.0-final?
Now consider the following markup:
<wicket:enclosure child="label1">
<span wicket:id="label1"></span>
<span wicket:id="label2"></span>
</wicket:enclosure>
When "label1" has its visibilty set to false a warning
"org.apache.wicket.Page - Component [Component id = label2, ...] wasn't
rendered but most likely it has a transparent parent: ..." is logged, which
in my opinion is a bit annoying. A log level of INFO or DEBUG would be more
appropriate, wouldn't it?
Best regards,
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
