orbednetwork / chrome-rest-client

Automatically exported from code.google.com/p/chrome-rest-client
0 stars 0 forks source link

XML is not shown for application/atom+xml content-type #100

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Send a get request to a server that sends an Atom respone, Content-Type 
=application/atom+xml;charset=utf-8 
2. The XML Tab only shows the pac-man symbol but no XML

What is the expected output? What do you see instead?
XML is shown as XML

Original issue reported on code.google.com by susanneu...@googlemail.com on 8 Nov 2012 at 2:44

GoogleCodeExporter commented 9 years ago
Is the console prints any error message? I tried to reproduce a problem and it 
works just fine even when I broke up xml body with not closed child or adding 
characters where it should not be. In worst case "Parsed" tab is shown instead 
of "XML".

Original comment by jarro...@gmail.com on 8 Nov 2012 at 8:20

GoogleCodeExporter commented 9 years ago
You can reproduce it by doing a GET request to 
http://services.odata.org/OData/OData.svc/Products(1)/Supplier/Products.

Original comment by Grogu...@gmail.com on 13 Nov 2012 at 10:36

GoogleCodeExporter commented 9 years ago
It is an error in background worker. However it use tinyxmlsax.js 
(http://xmljs.sourceforge.net/website/documentation-w3cdom.html) library to 
parse XML. This issue is a parsing error. This library throws a 
DOMException.NAMESPACE_ERR (in function DOMDocument.prototype.createElementNS). 
I will implement error catching in the worker and report an error in the 
application.

Original comment by jarro...@gmail.com on 13 Nov 2012 at 11:48

GoogleCodeExporter commented 9 years ago
Hello, I'm using your app to parse complex XML documents (with many namespaces 
)as result of REST queries ... And now I'm unable to see the XML response ( the 
raw response is there but not the parsed XML result).

Original comment by bey...@fresnes.info on 16 Nov 2012 at 6:20

GoogleCodeExporter commented 9 years ago
Same problem here.
Please prioritize, because the rest-client is nearly useless when working with 
atom format responses without an formatted output.

Thanks in advance

Original comment by alexande...@gmail.com on 23 Nov 2012 at 8:49

GoogleCodeExporter commented 9 years ago
It is fixed now. 
When background worker returns error it will use old parser (in UI thread) to 
parse XML document. It will be slower but it will be independent from XMLJS lib 
errors.

I updated the application in Web Store. You should have an update soon.

Original comment by jarro...@gmail.com on 23 Nov 2012 at 10:51

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r185.

Original comment by jarro...@gmail.com on 23 Nov 2012 at 11:23