Thanks, I thought this answer will come. Let me ask differently:
What is it which prevents Wicket applying the input on the first request?
What's the conceptual difference between creating a page, rendering a
page, receiving a request and applying the incoming data,
versus creating a page and applying the incoming data? Regardless of
whether there are stateful components or not.
Is this going to be targetted in the future?
I believe this has been discussed, so a link to such conversation is
appreciated.
Thanks!
Ondra
On 03/04/2013 03:27 PM, Martin Grigorov wrote:
Hi,
Make the page stateless, i.e. StatelessForm instead and avoid any other
stateful components.
On Mon, Mar 4, 2013 at 4:23 PM, Ondrej Zizka <[email protected]> wrote:
Hi all,
let's have a bookmarkable page with a form.
This form is submitted after session expiration.
The result is that Wicket ignores the input and renders the page as it was
just loaded by URL.
How can I make Wicket process the POST body and do the whole cycle - fill
the models, validate, etc.?
Thanks,
Ondra
------------------------------**------------------------------**---------
To unsubscribe, e-mail:
users-unsubscribe@wicket.**apache.org<[email protected]>
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
