This is because of your:
getSession().replaceSession();
call
You can change that in 2 ways
change the place where you call that so not at the beginning of the onsubmit
but completely at the end:
// Return onto the same page but disable inputField
setResponsePage(new HomePage(false, ++submitCount));
getSession().replaceSession();
then it works fine
The other is setting this setting:
protected void init() {
super.init();
getSessionSettings().setPageIdUniquePerSession(true);
}
I still dont know why that is not default to true
I think we should just drop the complete pagemap page id.
and always just use the session to create the next page id that is unique
across all sessions
Why do we have that setting? Matej was there really a thing that we still
need the page pagemap id?
johan
On Tue, Jan 6, 2009 at 13:58, Martin Makundi <
[email protected]> wrote:
> Hi!
>
> I have found out that the page set by setReponsePage does not process
> its own response and created a jira issue:
> https://issues.apache.org/jira/browse/WICKET-2006
>
> I also attached a wicket quickstart for easily repeating the problem:
>
> Press the form submit button once, and you will get a form with the
> input field disabled.
>
> You would assume pressing the button again, the page instance set in
> the "setResponsePage" method would process the form but NO, it is the
> original (first) page will process the form.. not knowing you have
> edisabled the field and any other problems that might result ..
>
> Is this a bug or a feature?
>
> **
> Martin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>