public Element[] process(Vector elems) throws Exception{}
It takes an array of DOM Elements because the SOAP body can have more than
one child element. If you're just passing an XML document, it'll only have
one child.
Check out the "message" directory in the Axis samples for a good
example. Note the deploy.wsdd file, which specifies that this service
should be treated as a message service rather than RPC.
Andrew
At 02:53 PM 7/24/2002 -0500, you wrote:
>thanks for the reply. What does your method signature look like for the
>method that recieves the document?
>
>-----Original Message-----
>From: Andrew Vardeman [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, July 24, 2002 2:52 PM
>To: [EMAIL PROTECTED]
>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
