You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by Mark Whitlock <ma...@uk.ibm.com> on 2005/05/20 17:58:52 UTC

Attachments in WS-I




I propose to add in support to wsdl2ws to allow mime bindings in the wsdl
binding so that attachments are described by the wsdl. Attachments are
passed to the client as a parameter on the web service itself.

This is required by WS-I
http://www.ws-i.org/Profiles/AttachmentsProfile-1.0-2004-08-24.html which
says in section 3.4 "Message with no attachments" "R2902 A SENDER MUST NOT
send a message using SOAP with Attachments if the corresponding wsdl:input
or wsdl:output element in the wsdl:binding does not specify the WSDL MIME
Binding" and then gives a doc-literal example in section 4.4 "Referencing
Attachments from the SOAP Envelope". If the attachment is an element in the
wsdl message, then I propose Axis C++ should represent it as a parameter on
the generated Stub web service invocation.

Comments?
Mark
Mark Whitlock
IBM


Re: Attachments in WS-I

Posted by Samisa Abeysinghe <sa...@gmail.com>.
+1 for taking mime bindings into account.

Samisa...

On 5/20/05, Mark Whitlock <ma...@uk.ibm.com> wrote:
> 
> 
> 
> 
> I propose to add in support to wsdl2ws to allow mime bindings in the wsdl
> binding so that attachments are described by the wsdl. Attachments are
> passed to the client as a parameter on the web service itself.
> 
> This is required by WS-I
> http://www.ws-i.org/Profiles/AttachmentsProfile-1.0-2004-08-24.html which
> says in section 3.4 "Message with no attachments" "R2902 A SENDER MUST NOT
> send a message using SOAP with Attachments if the corresponding wsdl:input
> or wsdl:output element in the wsdl:binding does not specify the WSDL MIME
> Binding" and then gives a doc-literal example in section 4.4 "Referencing
> Attachments from the SOAP Envelope". If the attachment is an element in the
> wsdl message, then I propose Axis C++ should represent it as a parameter on
> the generated Stub web service invocation.
> 
> Comments?
> Mark
> Mark Whitlock
> IBM
> 
>