[jira] Updated: (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 updated WICKET-1582: Fix Version/s: 1.4-M4 Affects Version/s: 1.4-M3 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.
[jira] Updated: (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 ] Martijn Dashorst updated WICKET-1582: - Fix Version/s: (was: 1.3.4) 1.3.5 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 Environment: Wicket 1.3-SNAPSHOT as of today Reporter: Nick Johnson Assignee: Maurice Marrink Fix For: 1.3.5 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.
[jira] Updated: (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 ] Johan Compagner updated WICKET-1582: Fix Version/s: 1.3.4 Assignee: Maurice Marrink 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 Environment: Wicket 1.3-SNAPSHOT as of today Reporter: Nick Johnson Assignee: Maurice Marrink Fix For: 1.3.4 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.
[jira] Updated: (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 ] Nick Johnson updated WICKET-1582: - Attachment: wicket1582.jar Simple test case showing nonequivalent behaviour between executeAjaxEvent(foo, onclick) and clickLink(foo). 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 Environment: Wicket 1.3-SNAPSHOT as of today Reporter: Nick Johnson 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.
