OK, the problem was an encoded german umlaut. E.g. the letter "ü" is (giving credit to the pred UTF-8 days) often encoded as ü in web pages. If the text is included in the XML response during an update, the XML engine of IE is stumbling about it.
As the default charset is UTF-8 anyway it's no big deal to send the decoded values. Anyway the error is hard to track down which makes it annoying. Regards, Markus On 1/17/07, Markus Joschko <[EMAIL PROTECTED]> wrote:
I run into the exact same issue. The error is only occuring using IE. Firefox is dealing fine with the response. Using fiddler I can see that there are actually ajax-response elements included, together with a lot of HTML as a big component is completely reloaded. So it looks as if the clientside can't deal with the update. Why does the code always break in IE where there is no tool like firebug to hunt the problem down? BTW, I use the 4.1.2-SNAPSHOT release. On 1/15/07, Stephane Decleire <[EMAIL PROTECTED]> wrote: > Thanks Jesse for your answer but it finaly seems that my "non response > received" error is due to non XML content : > I have <br> tags (not closed) in the HTML blocks that should be rendered > by the ResponseBuilder. These blocks are build with Tapestry @Insert > components with the raw parameter set to true. So other characters like > [ and ] also break the XML format ... > > Is there a way to render "raw content" via the ResponseBuilder ? (Is > JSON less strict on the format of the data ?) > > Thanks in advance. > > -- > Stéphane Decleire > > > > Jesse Kuhnert a écrit : > > I actually saw this today as well. Looks like it is (was) a bug in > > the ResponseBuilder logic associated with a recent flush() call change > > I made.. > > > > It's been fixed but only in a branch that no one can access yet. The > > real fix should come out within a week. (assuming that this is your > > problem, it may not be) > > > > On 1/12/07, andyhot <[EMAIL PROTECTED]> wrote: > >> Stephane Decleire wrote: > >> > Have you any idea of the cases where an Ajax request leads to the "No > >> > ajax-response elements recieved" error on the client ? > >> > > >> It should generally be an uncaught exception on the server-side code... > >> > >> Try to capture the actual ajax-response with a tool like FireBug and > >> just take a look at it > >> > >> -- > >> Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr > >> Tapestry / Tacos developer > >> Open Source / J2EE Consulting > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
