Jim...
You are correct.  With JAXM, you send the whole enchilada (envelope too).
Maybe this helps Steven, maybe not.
Stan

----- Original Message -----
From: "James McCarthy" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, March 12, 2002 5:27 PM
Subject: RE: document-style messaging and XML files


> Stan,
>
> I am not sure you can do this with JAXM. Unless I am mistaken the JAXM API
> requires that you send the entire SOAP content as an input stream. I am
> surprised that neither API allows you to specify just the BODY portion as
an
> input stream. Did I mis-read JAXM or is this the case?
>
> Jim
>
> Symmetry Solutions, Inc.
> http://www.symmetrysolutions.com/
>
> -----Original Message-----
> From: Stan Jordan [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 12, 2002 12:51 PM
> To: [EMAIL PROTECTED]
> Subject: Re: document-style messaging and XML files
>
>
> Steven...
> Good question.  You can do this with JAXM, and I would speculate that Axis
> may eventually
> support too.
> Cheers.
> Stan
>
> ----- Original Message -----
> From: "Steven Gollery" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, March 12, 2002 10:32 AM
> Subject: document-style messaging and XML files
>
>
> > I've been working on a service that uses document-style messaging to
> > return an XML file as the body of the message: I parse the file into a
> > Document and return that as the return value of the service (I'm using
> > alpha 3: I know that in the nightly build I would be sending the root
> > element as the first element of an array of Element objects).
> >
> > This all works fine, but I'm wondering if there is some other way to do
> > this. I mean: the file that I am sending already exists, so it seems
> > like I should be able to read the file (as text) and put it directly
> > into the SOAP message without going through the step of parsing it into
> > a Document. But I can't see how to do this: it looks to me like Axis
> > requires that I return a Document (or an array of Element objects) in
> > this situation.
> >
> > Any ideas?
> >
> > Steven Gollery
> > [EMAIL PROTECTED]
> >
> >
>
>

Reply via email to