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

Re: ampersand and friends - trace

Expand Messages
  • Simon Lok
    It appears that ampersand characters are not automatically encoded properly when using WSDLs... thanks to a tip about turning on tracing, I am able to include
    Message 1 of 6 , Oct 21, 2003
    • 0 Attachment
      It appears that ampersand characters are not
      automatically encoded properly when using
      WSDLs... thanks to a tip about turning on
      tracing, I am able to include the following dump
      SOAP message snippets...

      <SOAP-ENV:Body><namesp2:AddCompetitorType
      xmlns:namesp2="urn:ABC"><String_1
      xsi:type="xsd:string">176262029300358498510238664919063104555</
      String_1><String_2 xsi:type="xsd:string">a \& b</String_2></
      namesp2:AddCompetitorType></SOAP-ENV:Body>

      <SOAP-ENV:Body><namesp3:AddCompetitorType
      xmlns:namesp3="urn:ABC"><String_1
      xsi:type="xsd:string">176262029300358498510238664919063104555</
      String_1><String_2 xsi:type="xsd:string">a & b</String_2></
      namesp3:AddCompetitorType></SOAP-ENV:Body>

      Does anybody know how to turn on encoding
      of ampersands for WSDLs? I am also trying to run
      the same test using proxy and uri instead of
      using a WSDL but I am having some trouble
      getting that to work as well

      --SL
    Your message has been successfully submitted and would be delivered to recipients shortly.