IIRC the behavior used to be like that. But then someone decided that it is too fragile if you put your component into a repeater...
-Matej On 3/26/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
The current implementation of getMarkupId() is pretty dumb. It doesn't check if the user already has put a markup identifier in the page. This does not play nicely with page based, custom written javascript. I have several components of which I perfectly know that their id is unique, and reference them from javascript in the markup. Now if I attach a wicket ajax behavior to the component, I suddenly loose the markup identifier because Wicket insists on generating a unique one for me. Can we at least check if the component already has a markup attribute 'id', and if so, leave it alone? Martijn -- Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.5 will keep your server alive. Download Wicket now! http://wicketframework.org
