[
https://issues.apache.org/jira/browse/WICKET-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Makundi updated WICKET-2006:
-----------------------------------
Attachment: Wicket-Quickstart.zip
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 which will process the form.. not knowing you have edisabled the
field and any other problems that might result ..
> 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
> 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.
