Hi Eelco, > Well, what you can do is rather than using a generic > WebMarkupContainer, create a custom class that overrides > onComponentTagBody, create some interface for parameters that this > class understands, expose the ability to add instances of this > interface, and then when the component renders, let it loop through > these instances and print out the parameters. Sounds like a decent > solution to me tbh. Actually more explicit than allowing to add > behaviors that can alter the body.
since I haven't overridden onComponentTagBody yet - what happens to child-Tags then, do I have to manage these, too? E.g.: <object wicket:id="swf" movie="res/mymovie.swf" width="200" height="150"> <img src="res/alt-img.jpg" width="200" height="150"/> </object> Best regards, --- Jan. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
