Hi,
I don't think you're doing something weird, you're just seeing the
normal Wicket behavior:
>I debugged a bit
Good!
>that "success" calls though to some logic which marks my page as dirty
>generated a new version number, stores the changed page in the session
All pretty normal.
>I don't see anything to interfere with that
Why should you?
> the ctor of my page is not called again
> the same with onInitialization
Why should it?
Wicket is stateful by default, so it will keep the current page as long
as the user doesn't navigate away from it.
After form processing the input of all form components are cleared, but
after that you see the model values instead.
You can navigate to a new page instance
(#setResponsePage(this.getClass()) if you want to start over with empty
input *and* an empty model.
Regards
Sven
On 02.02.2015 18:34, Thorsten Schöning wrote:
Guten Tag Thorsten Schöning,
am Montag, 2. Februar 2015 um 18:13 schrieben Sie:
I do see the success message AND the values of the input which have
been sent.
I debugged a bit and can verify that "success" calls though to some
logic which marks my page as dirty, generated a new version number,
stores the changed page in the session and such. I don't see anything
to interfere with that and the ctor of my page is not called again,
the same with onInitialization, which I override to build my form.
I didn't see any code which resets the default model or its properties
or such.
Is all that expected and intended behavior or am I doing something
really weird? :-)
Mit freundlichen Grüßen,
Thorsten Schöning
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
