Yes, it is trivial. Just copy the code from the TransparentMarkupContainer (still on my disk).
As another option: In 1.5 we removed the final keyword from MarkupContainer.add(Component...) - see Border.java for the use case - so that in 1.5 you may also subclass add() and thus keep the markup and component hierarchies in sync. -Juergen On Mon, Nov 9, 2009 at 5:16 PM, Igor Vaynberg <igor.vaynb...@gmail.com> wrote: > you guys can still do that by allowing your webmarkupcontainer to > implement icomponentresolver instead of simply overriding > istransparentresolver(true). the impl itself should be trivia, just > check for the component in the page body. > > -igor > > On Mon, Nov 9, 2009 at 7:08 AM, Erik van Oosten <e.vanoos...@grons.nl> wrote: >> Ah yes, I do that as well. >> >> Regards, >> Erik. >> >> Olivier Croisier wrote: >>> >>> I use the same technique (WebMarkupContainer + isTransparentResolver=true) >>> on the <body> element to add an id attribute to it, with a unique value >>> for >>> each page extending the base template. This is useful to build unique CSS >>> selectors for each page. >>> >>> >> >> -- >> Erik van Oosten >> http://day-to-day-stuff.blogspot.com/ >> >> >> >
