Re: still having trouble with SOAP
Re: still having trouble with SOAP
- Subject: Re: still having trouble with SOAP
- From: "Mark J. Reed" <email@hidden>
- Date: Fri, 2 Sep 2005 16:45:58 -0400
On 9/2/05, Matt Neuburg <email@hidden> wrote:
> What I need to form, according to the authorities, is a request that looks
> like this:
>
> POST /WSShakespeare.asmx HTTP/1.1
> Host: www.xmlme.com
> Content-Type: text/xml; charset=utf-8
> Content-Length: length
> SOAPAction: "http://xmlme.com/WebServices/GetSpeech";
>
> <?xml version="1.0" encoding="utf-8"?>
> <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>
> <soap:Body>
> <GetSpeech xmlns="http://xmlme.com/WebServices";>
> <Request>string</Request>
> </GetSpeech>
> </soap:Body>
> </soap:Envelope>
> What I'm actually sending (snooped with Interarchy) looks more like this:
>
> POST /WSShakespeare.asmx HTTP/1.1
> User-Agent: Mac OS X; WebServicesCore.framework (1.1.0)
> Host: www.xmlme.com
> Content-Type: text/xml
> Soapaction: "http://xmlme.com/WebServices/GetSpeech";
> Content-Length: 608
> Connection: close
>
> <?xml version="1.0" encoding="UTF-8"?>
> <SOAP-ENV:Envelope
> xmlns:xsd="http://www.w3.org/1999/XMLSchema";
> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance";
> SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";>
> <SOAP-ENV:Body>
> <m:GetSpeech xmlns:m="http://xmlme.com/WebServices";>
> <Request xsi:type="xsd:string">poor and content is rich</Request>
> </m:GetSpeech>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
> Not very much alike, are they?
Actually, they seem identical in every way that counts. I don't see
any significant differences there:
SOAP doesn't care about user agents; if you're only making one
request, the Connection: close doesn't change anything; HTTP header
names are case-insensitive (although values aren't necessarily)...
Other than that, your authoritative example chose the name prefix
"soap" to associate with the SOAP Envelope namespace, while the XML
your AppleScript is generating uses "SOAP-ENV" - that's a completely
cosmetic distinction. The AppleScript XML is also specifying the
encoding, but that's certainly allowed; it's just optional.
Have you tried using this service from other SOAP client frameworks?
What exactly happens when you try it from AppleScript?
--
Mark J. Reed <email@hidden>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden