You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2010/08/28 23:17:08 UTC

[jira] Resolved: (WICKET-2379) Redirect fails wicketTest in rc7

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

Igor Vaynberg resolved WICKET-2379.
-----------------------------------

      Assignee: Igor Vaynberg
    Resolution: Won't Fix

there are indeed problems with sending a 302 as a response to an ajax call. some browsers take over and handle it automatically, but we need to be able to do some processing steps before we redirect.

you can easily validate the url happens like this:

assertEquals("http://testUrl", tester.getServletResponse().getHeader("Ajax-Location"));

> Redirect fails wicketTest in rc7
> --------------------------------
>
>                 Key: WICKET-2379
>                 URL: https://issues.apache.org/jira/browse/WICKET-2379
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4-RC7
>            Reporter: Martin Makundi
>            Assignee: Igor Vaynberg
>         Attachments: Wicket-Quickstart.zip
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> 1. click ajaxButton
> 2. redirect in button onSubmit
> 3. verify redirect in test <FAILS>
> See attached quickstart

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.