thinking out loud
in order make sure the associated markup is read just once, I'd
probably read the markup in the constructor not add().
compent names nested inside a wicket:component still need to be
unique, because wicket:components are "anonymous". Except you do
get("myBox").add(new Label("helloworld"...). correct?
Constructor will not read the markup, it will also add
<wicket:component>s which are immediate children (not nested
children).
container.add() checks against the Markup that the component name
exists. Else throw an error.
container.add() will also add <wicket:component>s which are immediate
children (not nested children) of the component just added (nested
components).
container would keep a transient ref to the Markup for the render process.
Though add() is available to valid that a component with the given
name is required, only render() (some method after constructor) is
able to validate that all components have been added.
Juergen
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user