not tried that; that is what GET is for (i.e. I return URLs to retrieve
stuff). Have a look at what the echo sample does
- Original Message -
From: "Mount, Dave" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, March 03, 2003 10:22
Subject: RE: Re: Fear of A
Steve,
I also found your article very helpful. Do you know how to send attachments back to
the client? This poses the same problem if you follow the 'echo' sample code.
I've tried adding it the same way that JAFDataHandlerSerializer does. That is:
Attachments attachments= context.getCurr
- Original Message -
From: "Mark Mueller" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, February 03, 2003 14:32
Subject: Re: Fear of Attachments
> Hi Steve,
>
> Thanks for the paper, it is helpful. I gather that it
> makes sense to supp
Hi Steve,
Thanks for the paper, it is helpful. I gather that it
makes sense to support both MIME and DIME attachments
in order to increase interoperability -- probably with
two different operations in order to be able to
specify the MIME-type of the MIME attachment in the
WSDL binding.
Your code
For all those people who want to do attachments, here is an early draft of
something I'm writing to look at attachments properly, including for .NET
and other platforms. Here is the Axis coverage; the code was working against
the CVS version of Axis this weekend; there have been changes in attachme
