and if such an exception is thrown then what? then you have to set them all by hand?
If by such a thing that in development you have a repeater or what ever that doesnt generate yet the second same id, but because of other larger data in production there is then suddenly in production an exception is thrown? That would be horrible. johan On Sat, Mar 8, 2008 at 7:10 AM, John Patterson <[EMAIL PROTECTED]> wrote: > > On 7 Mar 2008, at 23:52, Igor Vaynberg wrote: > >> > >> 100% agree. But you still should come with a solution that covers > >> that > >> without touching the IDs of the components on the page that > >> clearly won't > >> run into that issue. > > I think the ideal behaviour would be if Wicket always used the markup > id from the html if one is specified and threw an exception if the id > was used twice. But I don't know what problems exist in implementing > this. >
