I've implemented some extensions to <wicket:head> which I'd like you to test.
a) It is now possible (and allowed) to have multiple <wicket:head> tags per markup file b) markup inheritance (note: base and extended markup are merged at load time): <wicket:head> tags are no longer merged into a single <wicket:head> region, and as wicket:head tags now remember in which markup file they originally were in (base or extended) it was than possible to ensure that each wicket:head region contributes only once to the page's output (until now, common base markups contributed once per derived class) c) you may use <wicket:head wicket:scope="xxx"> to apply your own scope (default scope: null). This allows for more fine grained control. The key to distinguish the headers within each scope will be the java class name (of the markup file) d) You may implement WebMarkupContainerWithAssociatedMarkup.newHeaderPartContainer() and provide your own HeaderPartContainer which implements a more sophisticated scoping strategy Juergen ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
