Indeed so! Definitely more convincing. But given the request made, you should be able to capture the XML using wget or curl.
I'm just trying to offer you alternatives to getting there, hoping one of my ideas might make things easier for you. If it's a matter of not matching a spec, as opposed to not being able to parse it, that eliminates several of my thoughts as to cause. Does their spec indicate it makes use of XML namespaces? If so, have you called setNamespaceAware(true) on the XmlPullParserFactory? If this is a SOAP response, the data you expect may be buried down a level (or two, I forget; I guess it's been a while since I dealt with SOAP!). On Dec 1, 4:46 pm, Bret Foreman <[email protected]> wrote: > Bob, > > The server side is enterprise stuff - code that has been around for at > least a decade. I have no idea how the server-side engineers are > generating their XML, nor do I want to know. But what I've observed is > that the XML tree in the data I receive sometimes does not match the > documentation. In those cases, I need the enterprise people to fix > either the docs or their code. Either way, the best way to get them to > do that is to show them the actual XML received by the phone. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
