[
https://issues.apache.org/jira/browse/WICKET-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johan Compagner reassigned WICKET-2006:
---------------------------------------
Assignee: Matej Knopp
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?
So the only good fix that is see is drop the pagemap page id generator
completely
> The page set by setReponsePage does not process its own response.
> -----------------------------------------------------------------
>
> Key: WICKET-2006
> URL: https://issues.apache.org/jira/browse/WICKET-2006
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4-RC1
> Environment: Any
> Reporter: Martin Makundi
> Assignee: Matej Knopp
> Attachments: Wicket-Quickstart.zip
>
> Original Estimate: 12h
> Remaining Estimate: 12h
>
> Whenever the HomePage is submitted, it uses
> setResponsePage(new HomePage(xxx)); to open a new page in a new state.
> Whenever the form is submitted, the original page processes the form and thus
> any components that have changed state (e.g., become visible / invisible)
> remain in their original state and are not processed properly.
> More technically:
> The browser is viewing page instance X, but the form being processed belongs
> to the original page instance 0.
> It seems that the page set by setReponsePage does not process its own
> response.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
