* Gohan:
>
> "Label model does not match. expected:
> but was:"
> The problem seem to be that the call to ..setModelValue(..) doesn't update
> the model or it get "lost" when I press the submit button somehow. How can I
> fix this?
This is fixed in the soon-to-be-released Wicket 1.3
And please t
1.3 is currently a bit in flux
because of the backports and and the renaming so that naming is logical
But that should settle in a couple of weeks. And then we will also try to
release the first beta.
johan
On 4/5/07, Gohan <[EMAIL PROTECTED]> wrote:
Thanks for your reply. When is 1.3 going
Thanks for your reply. When is 1.3 going to be released? Is there a milestone
or release candidate version that you can download instead of downloading
the latest snapshot so I don't have to change my code all the time as with
wicket 2.0.
/Johan
Johan Compagner wrote:
>
> this looks more like
this looks more like a WicketTester failure then a failure of the real code
are you really porting to 1.2? You should try to go from 2.0 to 1.3 because
else you need
to change quite a lot more
johan
On 4/4/07, Gohan <[EMAIL PROTECTED]> wrote:
I'm porting an application from wicket 2.0 to 1.
I'm porting an application from wicket 2.0 to 1.2 but I run into trouble when
executing tests for some of the classes. The tests worked in Wicket 2.0.
Bellow is a simple example the demonstrate the problem:
public class FormPage extends WebPage {
private static final long serialVersionUI
