Why does the BODY allow an unused wicket:id attribute?
I was trying to implement an enhancement to my markup-inheritance-based pages to add a "class" attribute to the body tag in order to make it a little easier to apply my CSS. I added 'wicket:id="body"' to the body tag, and started adding a WebMarkupContainer. When I realized that all my child classes could no longer call "add()" directly because of the new hierarchy, I abandoned my attempt by removing these changes and redeploying. As I waited for the page to load, I remembered that I hadn't removed the attribute from the body tag, so I absolutely expected a Wicket exception. Instead, the page loaded fine.
So my first question is why don't I get an exception when there is a "wicket:id" attribute on the BODY tag and no corresponding Component on the Page?
My second question is whether there is an easy way to add or modify the "class" attribute (or the "id" attribute) of the BODY tag?
Any suggestions? The first question I suppose is mere curiousity, but I really would like to do the second.
Thanks, -- Scott ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
