I am still trying to understand why you think you need a seperate interface for getting the unique id. Component.getPath() gets you the unique id within the page already.
What we can do - and what we actually talked about doing in a distant past - is attaching an AttributeModifier (yes, I do like them) that appends an id attribute with that path value when some application wide setting is set. Because that is your only actual problem, right? That you don't want to attach AttributeModifiers all of the time, but instead want something that works out-of-the-box? Eelco ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
