You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Timo Rantalaiho (JIRA)" <ji...@apache.org> on 2008/10/14 09:41:44 UTC

[jira] Resolved: (WICKET-1582) WicketTester executeAjaxEvent onclick generating non-AJAX response

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

Timo Rantalaiho resolved WICKET-1582.
-------------------------------------

    Resolution: Fixed

Resolving for now to not block releases because of this. Please create a new issue if you're not happy with this workaround.

> WicketTester executeAjaxEvent onclick generating non-AJAX response
> ------------------------------------------------------------------
>
>                 Key: WICKET-1582
>                 URL: https://issues.apache.org/jira/browse/WICKET-1582
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.4, 1.4-M3
>         Environment: Wicket 1.3-SNAPSHOT as of today
>            Reporter: Nick Johnson
>            Assignee: Timo Rantalaiho
>             Fix For: 1.3.5, 1.4-M4
>
>         Attachments: wicket1582.jar
>
>
> Executing: 
> 		tester.executeAjaxEvent("linky", "onclick");
> 		tester.assertComponentOnAjaxResponse(component);
> throws an exception saying "The Previous response was not an AJAX response. You need to execute an AJAX event, using clickLink, before using this assert" although executeAjaxEvent should be resulting in an AJAX response (and prior to 1.3.3 it did).
> Executing tester.clickLink("linky"), which probably should be equivalent to the above executeAjaxEvent, does work.
> I'll attach a simple testcase demonstrating this behaviour.

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