[jira] Updated: (WICKET-2006) The page set by setReponsePage does not process its own response.

["Martin Makundi (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Makundi updated WICKET-2006:
-----------------------------------

    Description: 
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.

  was:
If FormTester is used twice or the same WicketTester and an involved form is updated (new visible/invisible components), the old form state prevails in tester.

Example:

[Login page, fields enabled]
Submit

[For some business logic reason, form is shown again but the fields are disabled]
Browser sees disabled fields. The form submitted via WicketTester sees enabled fields, i.e., the form processed by the wickettester is WRONG (wrong instance?).

        Summary: The page set by setReponsePage does not process its own response.  (was: If FormTester is used twice or the same WicketTester and an involved form is updated (new visible/invisible components), the old form state prevails in tester)

> 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.