[
https://issues.apache.org/jira/browse/WICKET-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-3442.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.5-RC2
Assignee: Igor Vaynberg
> setResponsePage() to mounted Page fails to redirect correctly
> -------------------------------------------------------------
>
> Key: WICKET-3442
> URL: https://issues.apache.org/jira/browse/WICKET-3442
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-RC1
> Environment: Reproduced this on Jetty 6.1.23 on Sun JDK on Ubuntu, as
> well as the Quickstart Jetty on Sun JDK on Windows 7
> Reporter: David Hansen
> Assignee: Igor Vaynberg
> Fix For: 1.5-RC2
>
> Attachments: brokenform.zip
>
>
> calling setResponsePage() within a Form#onSubmit( ) to a mounted Page will:
> 1. Not redirect to the mounted URI
> 2. Screw up path rewriting for all elements on the rendered page.
> I have attached a quickstart zipfile in which I am able to reproduce the
> issue. Here's a quick description of what happens:
> PageOne.class is mounted to /pageone
> PageTwo.class is mounted to /pagetwo
> PageOne has a Form with a single setResponsePage( PageTwo.class ); in its
> onSubmit( );
> When PageOne's form is submitted, instead of redirecting to /pagetwo, the
> page uri is something like /wicket/page?0-1.IFormSubmitListener-form
> Any subsequent path references on the rendering of PageTwo are broken, since
> the browser thinks the relative path origin is /wicket/, whereas wicket
> likely thinks it's /
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
