56 lines
2.9 KiB
HTML
56 lines
2.9 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>Pass SOAP messages with attachments using WSIF</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h5><A NAME="wswsifattwsif"></A>Pass SOAP messages with attachments using WSIF</h5>
|
||
|
|
|
||
|
|
<p><a target="_blank" href="http://www.w3.org/TR/SOAP-attachments">W3C SOAP Messages with Attachments</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center" border="0"> describes a standard way to associate a SOAP message with one or more attachments in
|
||
|
|
their native format (for example GIF or JPEG) by using a multipart MIME structure
|
||
|
|
for transport. It defines specific usage of the Multipart/Related MIME media
|
||
|
|
type and rules for the usage of URI references to refer to entities bundled
|
||
|
|
within the MIME package. It outlines a technique for a <a target="_blank" href="http://www.w3.org/TR/SOAP/">SOAP 1.1</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center" border="0"> message to be carried within
|
||
|
|
a MIME multipart/related message in such a way that the SOAP processing rules
|
||
|
|
for a standard SOAP message are not changed.</p>
|
||
|
|
|
||
|
|
<p>WSIF supports passing attachments in a MIME message using the
|
||
|
|
SOAP provider. For more information, see <a href="wswsifprovsp.htm">Use the SOAP provider</a>. The attachment is a <tt>javax.activation.DataHandler</tt>.
|
||
|
|
The <tt>mime:multipartRelated</tt>, <tt>mime:part</tt> and <tt>mime:content</tt> tags
|
||
|
|
are used to describe the attachment in the WSDL.</p>
|
||
|
|
|
||
|
|
<p>For more information, see the following topics:
|
||
|
|
<ul>
|
||
|
|
<li><a href="wswsifattwsdl.htm">SOAP messages with attachments
|
||
|
|
- writing the WSDL extensions</a>.</li>
|
||
|
|
<li><a href="wswsifattpass.htm">SOAP messages with attachments
|
||
|
|
- passing attachments to WSI</a>.</li>
|
||
|
|
<li><a href="wswsifattmap.htm">SOAP messages with attachments
|
||
|
|
- types and type mappings</a>.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>These scenarios are not supported:</p>
|
||
|
|
<ul>
|
||
|
|
<li>Using DIME.</li>
|
||
|
|
<li>Passing in <tt>javax.xml.transform.Source</tt> and <tt>javax.mail.internet.MimeMultipart</tt>.</li>
|
||
|
|
<li>Using the <tt>mime:mimeXml</tt> WSDL tag.</li>
|
||
|
|
<li>Nesting a <tt>mime:multipartRelated</tt> inside a <tt>mime:part</tt>.</li>
|
||
|
|
<li>Using types that extend <tt>DataHandler</tt>, <tt>Image</tt>, and so forth.</li>
|
||
|
|
<li>Using types that contain <tt>DataHandler</tt>, <tt>Image</tt>, and so
|
||
|
|
forth.</li>
|
||
|
|
<li>Using Arrays or Vectors of <tt>DataHandlers</tt>, <tt>Images</tt>, and
|
||
|
|
so forth.</li>
|
||
|
|
<li>Using multiple in/out or output attachments.</li>
|
||
|
|
</ul>The MIME headers from the incoming message are not preserved for referenced
|
||
|
|
attachments. The outgoing message contains new MIME headers for <tt>Content-Type</tt>, <tt>Content-Id</tt> and <tt>Content-Transfer-Encoding</tt> that
|
||
|
|
are created by WSIF.</p>
|
||
|
|
|
||
|
|
</body></html>
|