@Sven, Thanks for looking at it and the explanations.
On Wed, Mar 16, 2016 at 5:14 PM, Sven Meier (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/WICKET-6124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Sven Meier resolved WICKET-6124. > -------------------------------- > Resolution: Not A Problem > > The old behavior of WicketTester was wrong: it didn't set up the next > request whenever the current request couldn't be handled by Wicket. > > > wicket tested getLastResponse().getRedirectLocation() broken after > WICKET-5389 > > > ------------------------------------------------------------------------------ > > > > Key: WICKET-6124 > > URL: https://issues.apache.org/jira/browse/WICKET-6124 > > Project: Wicket > > Issue Type: Bug > > Components: wicket > > Affects Versions: 7.2.0 > > Reporter: Ernesto Reinaldo Barreiro > > Assignee: Sven Meier > > Priority: Minor > > > > Because of wicket WICKET-5389 getLastResponse().getRedirectLocation() > will return null after a redirect exception is thrown see discussion at > > http://markmail.org/message/wbavzriscdis22qv?q=wicket > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) > -- Regards - Ernesto Reinaldo Barreiro
