Yeah, if you do that then you have to make sure that it won't break when you e.g. put the component to page twice.
-Matej On 9/21/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > you can, but then good luck making sure they are unique... > > -igor > > > On 9/21/07, Ryan Sonnek <[EMAIL PROTECTED]> wrote: > > > > On 9/21/07, Matej Knopp <[EMAIL PROTECTED]> wrote: > > > > > > I dont' understand. You rely on the way how wicket generates IDs? Then > > > your code is bound to break. If you really need a wicket component's > > > id in javascript, you either override getMarkupId(), or pass the Id > > > using javascript (e.g. label component assigning another component's > > > id into javascript variable). > > > > > > You've got to be kidding me. You can just override getMarkupId() and > > avoid > > the mess of autogenerated wicket ids?? I never knew that! > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
