You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Andrei Badea (JIRA)" <ji...@apache.org> on 2013/04/24 11:11:16 UTC

[jira] [Created] (WICKET-5153) Wicket-atmosphere pushes empty messages

Andrei Badea created WICKET-5153:
------------------------------------

             Summary: Wicket-atmosphere pushes empty messages
                 Key: WICKET-5153
                 URL: https://issues.apache.org/jira/browse/WICKET-5153
             Project: Wicket
          Issue Type: Bug
          Components: wicket-atmosphere
    Affects Versions: 6.6.0
            Reporter: Andrei Badea
            Assignee: Emond Papegaaij


When filters filter out all subscriptions for a page, the logic around the ajaxRequestScheduled flag in AtmosphereRequestHandler prevents rendering the AjaxRequestHandler, which results in an emtpy response. This is pushed to the client and passed to the Wicket Ajax framework, which fails to parse it, because it expects it to be an XML document with ajax-response root element. This appears in the Wicket Ajax debug window:

ERROR: Wicket.Ajax.Call.failure: Error while parsing response: Could not find root <ajax-response> element

Note that because of

https://github.com/Atmosphere/atmosphere/issues/1042

Atmosphere does not pass the first empty message to callbacks, so the error above only happens when the second empty message is pushed.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira