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'trun 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.
