We have some older code that works with a web service via the CallHttp
API.
I am looking at some newer things and decided to look into using the
SOAP API instead of CallHttp mainly because I assumed that the SOAP API
would make things 'cleaner' in particular when accessing the returned
data.
However as far as I can tell, it has actually makes it messier.
Is there any way to extract just the return value from the response data
without having to muck around with the soap overhead ( envelopes etc ) ?
To me that should be the whole point in an API - to hide all that
plumbing.
For example, the response data from a web service returning a simple
string looks like this :
1 <?xml version="1.0" encoding="utf-8"?>
2 <soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
3 <soap:Body>
4 <HelloWorldResponse
xmlns="http://testservice.gerzio.ca/";>
5 <HelloWorldResult>Hello
World</HelloWorldResult>
6 </HelloWorldResponse>
7 </soap:Body>
8 </soap:Envelope>
The only thing that I am interested in is the single string value "Hello
World".
I guess I could locate <HelloWorldResult> & </HelloWorldResult> &
extract what is between them, but like I said , isn't that the whole
point in having an API ? Am I missing a step here - maybe I'm looking
at some out of date documentation ?
Gerry
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
