32 lines
1.4 KiB
HTML
32 lines
1.4 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>Types and type mappings</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h5><A NAME="wswsifattmap"></A>Types and type mappings</h5>
|
||
|
|
|
||
|
|
<p><strong>Note:</strong> This page applies to WebSphere Application Server - Express Version 5.0.2 and later only.</p>
|
||
|
|
|
||
|
|
<p>By default, attachments are passed into WSIF as <tt>DataHandlers</tt>.
|
||
|
|
If the part on the message which is the <tt>DataHandler</tt> maps to a <tt>mime:part</tt> in
|
||
|
|
the WSDL, then WSIF automatically maps the fully qualified name of the
|
||
|
|
WSDL type to <tt>DataHandler.class</tt> and sets up that type mapping with
|
||
|
|
the SOAP provider.</p>
|
||
|
|
|
||
|
|
<p>In your WSDL, you may have defined a schema for the attachment
|
||
|
|
(for instance as a <tt>binary[]</tt>). Whether or not you have done this,
|
||
|
|
WSIF silently ignores this mapping and treats the attachment as a <tt>DataHandler</tt>,
|
||
|
|
unless you have explicitly issued <tt>mapType()</tt>. WSIF lets the SOAP provider set the
|
||
|
|
MIME content type based on the type of the <tt>DataHandler</tt>,
|
||
|
|
instead of the <tt>mime:content</tt> type specified in the WSDL. </p>
|
||
|
|
|
||
|
|
</body></html>
|