62 lines
3.0 KiB
HTML
62 lines
3.0 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
|
||
|
|
<title>Write the WSDL extensions</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h5><A NAME="wswsifattwsdl"></A>Write the WSDL extensions</h5>
|
||
|
|
<p><strong>Note:</strong> This page applies to WebSphere Application Server - Express Version 5.0.2 and later only.</p>
|
||
|
|
|
||
|
|
<p>The following WSDL illustrates a simple operation that has one attachment called <tt>attch</tt>:</p>
|
||
|
|
<pre><binding name="MyBinding" type="tns:abc" >
|
||
|
|
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
|
||
|
|
<operation name="MyOperation">
|
||
|
|
<soap:operation soapAction=""/>
|
||
|
|
<input>
|
||
|
|
<mime:multipartRelated>
|
||
|
|
<mime:part>
|
||
|
|
<soap:body use="encoded" namespace="http://mynamespace"
|
||
|
|
encodingStyle="http://schemas.xmlsoap.org/soap/encoding"/>
|
||
|
|
</mime:part>
|
||
|
|
<mime:part>
|
||
|
|
<mime:content part="attch" type="text/html"/>
|
||
|
|
</mime:part>
|
||
|
|
</mime:multipartRelated>
|
||
|
|
</input>
|
||
|
|
</operation>
|
||
|
|
</binding>
|
||
|
|
</pre>
|
||
|
|
<p><strong>Notes:</strong>
|
||
|
|
<ul>
|
||
|
|
<li>There must be a <tt>part</tt> (in this example <tt>attch</tt>) on the
|
||
|
|
input message for the operation (in this example <tt>MyOperation</tt>). There
|
||
|
|
can be other input parts to <tt>MyOperation</tt> that are not attachments.</li>
|
||
|
|
<li>In the binding input there must either be a <tt><soap:body</tt> tag
|
||
|
|
or a <tt><mime:multipartRelated</tt> tag, but not both.</li>
|
||
|
|
<li>For MIME messages, the <tt>soap:body</tt> is inside a <tt>mime:part</tt>.
|
||
|
|
There must only be one <tt>mime:part</tt> that contains a <tt>soap:body</tt> in
|
||
|
|
the binding input and that must not contain a <tt>mime:content</tt> as well,
|
||
|
|
because a content type of <tt>text/xml</tt> is assumed for the <tt>soap:body</tt>.</li>
|
||
|
|
<li>There can be multiple attachments in a MIME message, each described by
|
||
|
|
a <tt>mime:part</tt>.</li>
|
||
|
|
<li>Each <tt>mime:part</tt> (that is not a <tt>soap:body</tt>) contains a
|
||
|
|
<tt>mime:content</tt> that describes the attachment itself. The <tt>type</tt> attribute
|
||
|
|
inside the <tt>mime:content</tt> is not checked or used by WSIF. It is there
|
||
|
|
to suggest to the application using WSIF what the attachment contains. Multiple <tt>mime:contents</tt> inside
|
||
|
|
a single <tt>mime:part</tt> means that the backend service expecta a single
|
||
|
|
attachment with a type specified by one of the <tt>mime:contents</tt> inside
|
||
|
|
that <tt>mime:part</tt>.</li>
|
||
|
|
<li>The <tt>parts="..."</tt> attribute (optional) inside the <tt>soap:body</tt> is
|
||
|
|
assumed to contain the names of all the MIME parts as well as the names of
|
||
|
|
all the SOAP parts in the message.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
</body></html>
|