I found the link to the wiki page explaining how to fix this: https://github.com/Atmosphere/atmosphere/wiki/Multiply-messages-arrives-as- single-response-body-or-message-received-are-incomplete
It seems the trackMessageLength option needs to be enabled in the js, and some additional code is needed server side. From what I see, neither one will work without the other. Can you try if the solution provided at wiki works? To pass the additional option in the js, just copy jquery.wicketatmosphere.js, add the parameter and register the new file as a replacement resource in the application. Also please create a Jira issue for this. If you could post your findings there, that would help me tremendously, because my time to work on Wicket is very limited at the moment. Best regards, Emond On Tuesday 13 November 2012 16:03:30 Martin Grigorov wrote: > The problem is that Atmosphere sends the response in chunks. > Jean Francois explained in Atmosphere mailing lists that a special > Atmosphere has to be used that will collect the whole response before > flushing it. > > > On Tue, Nov 13, 2012 at 3:25 PM, Emond Papegaaij <emond.papega...@topicus.nl > > wrote: > > > > This is most likely caused by incorrect escaping, which might be a bug in > > Wicket or Wicket-Atmosphere. Can you try to create a quickstart to > > demonstrate > > the problem and file a Jira ticket? You can use the example application at > > https://github.com/papegaaij/wicket-atmosphere-quickstart > > > > Best regards, > > Emond > > > > On Sunday 11 November 2012 18:03:52 Pierre Goupil wrote: > > > Hi all, > > > > > > When I submit complex JS to my client using target.appendJavaScript() > > > > with > > > > > a @Subscribe method from Wicket-Atmosphere, I got this message in the > > > browser console: > > > > > > Wicket.Ajax: Wicket.Ajax.Call.failure: Error while parsing response: > > > Could not find root <ajax-response> element > > > > > > I do have an <ajax-response> tag and the response from the server seems > > > > to > > > > > be all OK. Nonetheless, for a reason I'm not aware of, it fails. > > > > > > Did anyone encounter this error before? Is there a known work-around? > > > > > > When I have a simple response, it works though. The problem only occurs > > > with complex responses. > > > > > > I'm using: > > > <wicket.version>6.3.0-SNAPSHOT</wicket.version> > > > <wicketstuff.version>6.2.1</wicketstuff.version> > > > > <wicket-atmosphere.version>0.5-SNAPSHOT</wicket-atmosphere.version> > > > > > (GIT master) > > > > > > Regards, > > > > > > Pierre
