T
Toby
I'm in the midst of implementing a Office Outlook 2007 Mobile Service (OMS)
backend to allow Office to connect to our two-way SMS gateway using the
guidelines published here:
http://www.microsoft.com/downloads/...a6-5598-4fd8-a448-820d8bae5f07&displaylang=en
You'll notice from the WSDL in that document that Outlook wants a simple
string back from each request containing an XML document - it doesn't want
proper SOAP-managed parameters.
I have the SOAP backend working to the document's specifications except one
important requirement in the document that has me baffled:
"Developers should also be aware that:
• ServiceInfo is transferred as a Unicode string, and then encoded as utf-16"
What exactly does this mean? Looking at the logs, the SOAP request arriving
at my server from Office when it attempts to register my OMS is utf-8 encoded
XML as I would expect for any SOAP request. So what does it want back?
- A utf-8 encoded SOAP envelope containing a utf-8 encoded XML string
(don't think so - the specifications clear say it wants utf-16)
- A utf-16 encoded SOAP envelope containing a utf-18 encoded XML string
(sounds good to me, but that doesn't explain the "and then encoded..." part
of the requirement above)
- A utf-8 encoded SOAP envelope containing a Unicode-escaped XML string
(eg. \u003c\u003f\u0078\u006d...)
I have tried feeding all the above formats back, and each time, I receive
the generic "Outlook did not receive response from the Web Service because of
a problem connecting to the server. Try again later." I really believe this
error to be a misnomer - although it claims not to be able to connect, I can
clearly see the connection and SOAP request arriving at my server. I can only
assume that Outlook doesn't like the response format I'm sending, and the
only place I can see that I'm out of conformance with the documentation is in
the encoding.
Any suggestions here? I would really appreciate feedback on which of the
above formats Outlook is expecting back, and if there's any way of debugging
the Outlook side of the connection.
Thanks!
Toby.
backend to allow Office to connect to our two-way SMS gateway using the
guidelines published here:
http://www.microsoft.com/downloads/...a6-5598-4fd8-a448-820d8bae5f07&displaylang=en
You'll notice from the WSDL in that document that Outlook wants a simple
string back from each request containing an XML document - it doesn't want
proper SOAP-managed parameters.
I have the SOAP backend working to the document's specifications except one
important requirement in the document that has me baffled:
"Developers should also be aware that:
• ServiceInfo is transferred as a Unicode string, and then encoded as utf-16"
What exactly does this mean? Looking at the logs, the SOAP request arriving
at my server from Office when it attempts to register my OMS is utf-8 encoded
XML as I would expect for any SOAP request. So what does it want back?
- A utf-8 encoded SOAP envelope containing a utf-8 encoded XML string
(don't think so - the specifications clear say it wants utf-16)
- A utf-16 encoded SOAP envelope containing a utf-18 encoded XML string
(sounds good to me, but that doesn't explain the "and then encoded..." part
of the requirement above)
- A utf-8 encoded SOAP envelope containing a Unicode-escaped XML string
(eg. \u003c\u003f\u0078\u006d...)
I have tried feeding all the above formats back, and each time, I receive
the generic "Outlook did not receive response from the Web Service because of
a problem connecting to the server. Try again later." I really believe this
error to be a misnomer - although it claims not to be able to connect, I can
clearly see the connection and SOAP request arriving at my server. I can only
assume that Outlook doesn't like the response format I'm sending, and the
only place I can see that I'm out of conformance with the documentation is in
the encoding.
Any suggestions here? I would really appreciate feedback on which of the
above formats Outlook is expecting back, and if there's any way of debugging
the Outlook side of the connection.
Thanks!
Toby.