Thanks Dave, that's what I thought, the soap api is a half-assed implementation that requires the user to have intimate knowledge of the soap data structures.
So far I see no advantage to using the SOAP api over callHttp. Imo, the samples on the ibm are a joke, for example, besides the fact that the examples blow up in numerous places, the SOAP example calls a web service by actually building the ENTIRE soap message manually - what exactly is the point in that ? isn't that what the soap api is for - so that you don't have to know any of the soap structural details ? if the example had demonstrated how to set parameters using the api instead of hand coding the entire SOAP message it would make a lot more sense. And so ends my bad-day rant. Gerry -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Davis Sent: June 1, 2007 2:45 PM To: [email protected] Subject: RE: [U2] SOAP API You get that string, but there are commands you can use which parse it into ordinary dynamic arrays. Look at the XDOM and XMAP related commands. IBM has sample basic code posted on their site that shows you how to get what you want. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of gerry-u2ug Sent: Friday, June 01, 2007 2:19 PM To: [email protected] Subject: [U2] SOAP API 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/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
