Re: Passing XML in a RPC Parameter

I actually have the XML string in a text file right now for simplicity and
read it in and send it.  I've also built it using a DOM library as well.

From what I've heard back from others you should always have to encode the
entire XML string when using an RPC style of communication.  This seems to
be part of the SOAP Standard which is what I'm trying to read through right
now.

It seems when using RPC the values of parameters should not be XML.  As you
saw previously Dick Brooks response suggests using SwA when passing XML
documents through an RPC interface.

Ryan

-----Original Message-----
From: Peter Thaggard [mailto:[email protected]]
Sent: Tuesday, January 06, 2004 3:59 PM
To: [email protected]
Subject: Re: [SOAP] Passing XML in a RPC Parameter


How are you constructing the XML String?  We use the Microsoft DOMDocument
object, and then call its .xml method, which
yields a well-formatted String manifestation of the DOMDocument.






                      "Ryan Champlin"
                      <ryan.champlin@FIRS        To:
[email protected]
                      TLOGIC.COM>                cc:
                      Sent by:                   Subject:  Re: [SOAP]
Passing XML in a RPC Parameter
                      "Discussion of
                      implementing SOAP
                      applications today"
                      <[email protected]
                      OP.COM>


                      01/06/2004 02:18 PM
                      Please respond to
                      "Discussion of
                      implementing SOAP
                      applications today"






That is how we have it defined.  However when I pass it as straight XML it
is not being handled correctly by the .Net web serivce.
It seems that in order for it to recognize the XML I need to encode
(Convert
symbols such as "<" to "&lt;" etc..) the entire string.
Then the web service seems to be able to handle the string argument we are
passing.  It seems that something on the web service side of things is
expecting to unecode that string parameter and expecting it to be encoded.
I'm trying to find out if that is part of the standard.  Should be always
have to encode that entire string to be compliant with the standard?

Thanks,
Ryan

-----Original Message-----
From: Peter Thaggard [mailto:[email protected]]
Sent: Tuesday, January 06, 2004 1:14 PM
To: [email protected]
Subject: Re: [SOAP] Passing XML in a RPC Parameter


Hello,

Yes, we do this all the time; in fact, we convert 40,000-row Excel
spreadsheets into XML,
which is then passed to a Java-based web service.

Just define your Web Service to accept a String argument.





                      "Ryan Champlin"
                      <ryan.champlin@FIRS        To:
[email protected]
                      TLOGIC.COM>                cc:
                      Sent by:                   Subject:  [SOAP] Passing
XML in a RPC Parameter
                      "Discussion of
                      implementing SOAP
                      applications today"
                      <[email protected]
                      OP.COM>


                      01/06/2004 01:47 PM
                      Please respond to
                      "Discussion of
                      implementing SOAP
                      applications today"






Is it possible to pass an XML document in a parameter of an RPC style web
service method that is expecting a string?  If so what is the
proper procedure for doing this?

When testing various clients we are finding out that we need to encode the
entire XML string in order for this to work.  The web service itself was
developed
using the .Net platform.

Thanks,
Ryan