[
https://issues.apache.org/jira/browse/WICKET-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johan Compagner closed WICKET-2006.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.4-RC2
1.3.6
Assignee: Johan Compagner (was: Matej Knopp)
fixed it so that page id's are always session specific so that they never
overlap by accident
> 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: Johan Compagner
> Fix For: 1.3.6, 1.4-RC2
>
> 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.
