search

hadoop-cloud / odata4j

Automatically exported from code.google.com/p/odata4j
0 stars 0 forks source link

Parse complex <innererror> properly out of error responses #202

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
<innererror> can be arbitrary xml content, not just text.

e.g. http://data.stackexchange.com/stackoverflow/atom/Votes

Our consumer does not parse these properly.  To fix:
  - introduce Characters2 to our shadow stax api (to mirror javax.xml.stream.events.Characters)
  - introduce isCharacters, asCharacters to our xml event
  - create innerXml, outerXml helpers sitting on top of our stax api
  - use innerXml when parsing <innererror>, not getElementText

Original issue reported on code.google.com by john.spurlock on 6 Aug 2012 at 11:38

GoogleCodeExporter commented 8 years ago 
This issue was closed by revision f9683472bdc6.

Original comment by john.spurlock on 7 Aug 2012 at 12:18