Re: Wicket 1.5 markup id for a reused TextField is the same

2012-04-09 Thread Martin Grigorov
On Tue, Apr 10, 2012 at 7:38 AM, Wilhelmsen Tor Iver wrote: >> In 1.4 version of wicket there was no impact, but in 1.5.5 the id is not >> overwritten by wicket. > > Presumably they changed it so that it would work as a markup equivalent to > setMarkupId(), though I haven't checked the changes l

RE: Wicket 1.5 markup id for a reused TextField is the same

2012-04-09 Thread Wilhelmsen Tor Iver
> In 1.4 version of wicket there was no impact, but in 1.5.5 the id is not > overwritten by wicket. Presumably they changed it so that it would work as a markup equivalent to setMarkupId(), though I haven't checked the changes list to verify that. :) - Tor Iver ---

Re: Wicket 1.5 markup id for a reused TextField is the same

2012-04-09 Thread dpmihai
I found the problem. Inside html I also had the id like: In 1.4 version of wicket there was no impact, but in 1.5.5 the id is not overwritten by wicket. So I removed it, and everything is ok. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-markup-id-for