I had interoperability issues the MSTK when specifying the XML as doc/lit in an RPC response. I ended up punting and just XML encoding the doc to send it as a string like Andrew mentioned. I've never tried this with .NET.
Les ----- Original Message ----- From: "Andrew Vardeman" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 24, 2002 12:51 PM Subject: Re: passing xml documents > I'm passing XML documents back and forth between Axis and .NET using > doc/lit (message style). I figured it was the most natural way to go since > the SOAP envelope is XML. Axis makes doc/lit really easy; .NET is so bent > on serializing and deserializing everything for you that it took some work > figuring out how to give it an XML document and say "just stick this in the > SOAP Body." RPC works fine too (just XML-encode the document to escape > the >'s, &'s, etc. and send it as a string), and it might save you some > hassle, but the escaping will make your messages a little longer if size is > important. I guess it depends on what you plan to do with the document > when it gets to the other end... > > Andrew > > At 02:37 PM 7/24/2002 -0500, you wrote: > >i'm trying to figure out the best way to do this. Has anyone implemented a > >web service with axis where you pass an entire xml document as the payload? > >if so, did you use a rpc style or a message style service? > > > >thanks! > >mark > > > >
