Comments on: Parsing XML: jQuery vs. ExtJS

By: Erik

Erik — Fri, 24 Jul 2009 02:22:50 +0000

http://support.microsoft.com/kb/306355

Now your error page can have valid HTML, XHTML or whatever you want in it. You can even make a nice user-friendly message instead of an error dump.

By: Art

Art — Fri, 19 Jun 2009 14:51:08 +0000

I solved this by using simple regular expressions, though I’m still unhappy ExtJS doesn’t have a built-in utility to clean my DOM string (the cause of the problem).

*edit: I can’t post the regular expression because WordPress interprets it as HTML. Check the link in the post to the ExtJS forum and you’ll see my solution.

By: Art

Art — Thu, 18 Jun 2009 20:37:23 +0000

@extidiot: That is a nice solution, but the problem is that (1) I’m not returned valid XML code, and (2) the responseText attribute has an HTML tag, which can’t be a child of DIV. Thus Ext.DomQuery.selectValue() doesn’t seem to work – it actually sets the value to “undefined”.

@wregen: Also a nice solution. Same problem though…

The problem lies in the fact that my response.responseText value isn’t valid XML and needs to be cleaned.

I’m looking into forcing .NET to return the error differently, so I’ll let you know what happens.

By: wregen

wregen — Thu, 18 Jun 2009 15:48:13 +0000

I’ve faced similar problems. My solution was to actually put the response into DOM.
Something like:

Ext.get(‘proxy-element’).update(the-response);

And then I am able to use: Ext.DomQuery. I did not think about elegance of my solution… perhaps I should?

By: extidiot

extidiot — Thu, 18 Jun 2009 14:56:37 +0000

And if it is valid XML, then you can use responseXML and DomQuery will understand it!

By: extidiot

extidiot — Thu, 18 Jun 2009 14:22:48 +0000

Doesn’t it seem obvious?

var d = document.createElement(“div”);
d.innerHTML = response.responseText;
errorMessage = Ext.DomQuery.selectValue(“div#errortext”, d);