W3C home > Mailing lists > Public > xml-dist-app@w3.org > January 2001

FW: [SOAP] SOAP method parameter as XML string - Question ?

From: Dick Brooks <dick@8760.com>
Date: Fri, 26 Jan 2001 06:58:36 -0600
To: "XP-PUBLIC" <xml-dist-app@w3.org>
Message-ID: <NDBBIOBLMLCDOHCHIKMGMEBKFCAA.dick@8760.com>
Here is a use case from the SOAP listserv indicating the need to encapsulate
XML payloads. You can see by his question regarding CDATA "escaping" that XP
needs to be precise in defining a method for packaging XML documents,
especially those that contain PI's, DOCTYPE's and CDATA sections.



Dick Brooks
Group 8760
110 12th Street North
Birmingham, AL 35203
dick@8760.com
205-250-8053
Fax: 205-250-8057
http://www.8760.com/

InsideAgent - Empowering e-commerce solutions

  -----Original Message-----
  From: SOAP [mailto:SOAP@DISCUSS.DEVELOP.COM]On Behalf Of Miles Blanc
  Sent: Friday, January 26, 2001 2:16 AM
  To: SOAP@DISCUSS.DEVELOP.COM
  Subject: [SOAP] SOAP method parameter as XML string - Question ?


  Hi all,

  I am using the XMLHttpRequest object to send all our SOAP
  requests to an ASP listener deployed on the Server. Right
  now, Our requirements dictate that we not use any commercial
  toolkits. However, we might be using one of the available
  toolkits such as the MS toolkit or the Apache XML toolkit.
  The actual implementation of the exposed service is in a
  COM object hosted in an NT Service.
  The ASP listener fowards the requests to the COM objects
  deployed hosted in the NT Service.
  Most of these COM objects' method parameters take just
  XML strings.

  eg : GetEmpList([in] BSTR bstrXMLCategory. [out,retval]
      BSTR* pBstrXMLEmpList)

  Question :

  My question is will passing the XML string parameter in the
  SOAP envelope have any problem ?. (I remember some earlier
  discussions -  limitations in some toolkits that you
  had to wrap any XML params being passed into CDATA sections)

  THis would definitely work in our case since we are not using
  any toolkits for our mapping needs. However, we need to
  generate SOAP envelopes that would interoperate with most
  of the commercial toolkits available so that any migration
  efforts would be easy later on.

  For the <Category> parameter in the below example,we are passing
  a parameter that is itself an XML string. Will this cause any
  problems ?. Should it be wrapped under a CDATA section.

  Here is a sample SOAP request :

  <SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
   SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
      <SOAP-ENV:Header></SOAP-ENV:Header>

      <SOAP-ENV:Body>
          <m:GetEmpList xmlns:m="urn:mycompany.com">
              <Category>

    <ThisIsTheActualXMLParamString>
    <SomeXMLData></SomeXMLData>
    </ThisIsTheActualXMLParamString>

      </Category>

          </m:GetEmpList>
      </SOAP-ENV:Body>
  </SOAP-ENV:Envelope>


  Thanks,
  Miles
Received on Friday, 26 January 2001 08:02:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:58 GMT