Loading ...
Sorry, an error occurred while loading the content.

Re: [soapbuilders] White Mesa doesn't like charset=UTF-8 ?

Expand Messages
  • Bob Cunnings
    Hello, That s odd! It shouldn t care... to be honest, the charset parameter is ignored at the moment and the parser checks for the presence of a (UTF-16
    Message 1 of 2 , Apr 2, 2001
    • 0 Attachment
      Hello,

      That's odd! It shouldn't care... to be honest, the charset parameter
      is ignored at the moment and the parser checks for the presence of
      a (UTF-16 encoded) BOM to determine whether or not the input is
      UTF-16. Otherwise it is treated as UTF-8 and converted to Unicode
      for internal processing.

      I'll have to look into it.

      RC

      > Here's the test results for White Mesa with a Content-Type=text/xml
      > header
      >
      > White Mesa SOAP RPC 1.4
      > -----------------------
      > EchoVoid passed
      > EchoString passed
      > EchoInteger passed
      > EchoFloat passed
      > EchoStruct failed SOAP-ENV:Client : Encountered unsupported data type
      > namespace.
      > EchoStringArray passed
      > EchoIntegerArray passed
      > EchoFloatArray passed
      > EchoStruct failed SOAP-ENV:Client : Encountered unsupported data type
      > namespace.
      > NoSuchMethod failed, HTTP status code was 404 expected 500
      >
      > And if i modify the client to send a Content-Type=text/xml;
      > charset=UTF-8, i get (note that EchoInteger now fails)
      >
      > White Mesa SOAP RPC 1.4
      > -----------------------
      > EchoVoid passed
      > EchoString passed
      > EchoInteger failed SOAP-ENV:Server : XML Parser: Parse Error on Line
      > 1.
      > EchoFloat passed
      > EchoStruct failed SOAP-ENV:Client : Encountered unsupported data type
      > namespace.
      > EchoStringArray passed
      > EchoIntegerArray passed
      > EchoFloatArray passed
      > EchoStruct failed SOAP-ENV:Client : Encountered unsupported data type
      > namespace.
      > NoSuchMethod failed, HTTP status code was 404 expected 500
      >
      > Here's a wiredump for the failing EchoInteger
      > POST http://services2.xmethods.net:8080/interop HTTP/1.0
      > Content-Type: text/xml; charset=UTF-8
      > User-Agent: pocketSOAP 0.9.2
      > Host: services2.xmethods.net:8080
      > Content-Length: 436
      > SOAPAction: "urn:interopLab#echoInteger"
      >
      > <S:Envelope xmlns:S='http://schemas.xmlsoap.org/soap/envelope/'
      > xmlns:SOAP-ENC='http://schemas.xmlsoap.org/soap/encoding/'
      > S:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'
      > xmlns:xsd='http://www.w3.org/1999/XMLSchema'
      > xmlns:xsi='http://www.w3.org/1999/XMLSchema-instance'>
      > <S:Body>
      > <m:echoInteger xmlns:m='urn:xmethodsInterop'><inputInteger
      > xsi:type='xsd:int'>-32768</inputInteger></m:echoInteger>
      > </S:Body></S:Envelope>
      >
      >
      > Cheers
      > Simon
      >
      >
      > To unsubscribe from this group, send an email to:
      > soapbuilders-unsubscribe@yahoogroups.com
      >
      >
      >
      > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.