Currently Component.java maintains a copy-on-write ValueMap for markup attributes which user might want to change, such as getMarkupId() which adds the id="xxx" attribute to the tag.
However, the current implementation doesn't work properly as the Component owned attribute map keep the "old" value even when the markup has been re-loaded because of locale, style or variation changes (see FormExample) I wonder if this general use case of being able to modify any tag attribute in the constructor realy exists or if "id" is the only case. If the latter is true, than I would like to suggest to remove markupAttribute from Component as it requires some realy hackish code later on. I'd much rather add a "id" variable to the component for the specific purpose of MarkupId().. What do think? Juergen ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
