You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Steve Loughran <st...@iseran.com> on 2003/02/03 20:01:49 UTC
Fear of Attachments
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 attachment
support since the 1.1 beta.
There is no scheduled release date for the full paper, it depends on when I
get round to it.
-Steve
Re: Fear of Attachments
Posted by Steve Loughran <st...@iseran.com>.
----- Original Message -----
From: "Mark Mueller" <ma...@yahoo.com>
To: <ax...@xml.apache.org>
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 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 samples are useful, but I'd really like to
> see the WSDL. I am leery of using "DataHandler" in my
> WSDL because it seems Java-specific. I like the idea
> of specifying the attachment file type as "anyType" in
> the message description and describing the mime-type
> as "application/octet-stream" because it "feels"
> generic and WSDL2Java creates a nice client which
> handles the attachment. The only qualm I have is that
> the client maps the mime-part to an Object which may
> not be very efficient.
>
> Mark
There is no WSDL. Or to be precise, attachments arent in the signature thta
WSDL knows about. I am just tacking them into the call before I make the
request, and on the receiving end I pull out the attachments after the RPC
invocation does it work of calling my method
Re: Fear of Attachments
Posted by Mark Mueller <ma...@yahoo.com>.
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 samples are useful, but I'd really like to
see the WSDL. I am leery of using "DataHandler" in my
WSDL because it seems Java-specific. I like the idea
of specifying the attachment file type as "anyType" in
the message description and describing the mime-type
as "application/octet-stream" because it "feels"
generic and WSDL2Java creates a nice client which
handles the attachment. The only qualm I have is that
the client maps the mime-part to an Object which may
not be very efficient.
Mark
--- Steve Loughran <st...@iseran.com> wrote:
> 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 attachment
> support since the 1.1 beta.
>
> There is no scheduled release date for the full
> paper, it depends on when I
> get round to it.
>
> -Steve
>
> ATTACHMENT part 2 application/pdf name=Fear of
Attachments.pdf
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com