A MIME part has one route part and none or more attachment parts.

The route part is defined in the beginning of the MIME part. After the route part, the attachment part is defined.

In the attachment part, the arguments or return values specified in the Java interface are mapped. The following table describes the mapping between the contents specified in the Java interface and the definition sequence in the attachments.

Table 30-9 Contents specified in the Java interface and the definition sequence in the attachment part

The following figure shows an example of mapping the Java interface to the attachment part.

Figure 30-3 Java interface and attachment mapping: Example

When the attachment is of MTOM/XOP specification format, the XOP information set defined in the XOP specifications is used for mapping the route part to the attachment. The XOP information is coded in the SOAP body of the route part, and the Content-Id of the corresponding attachment is set. The corresponding attachment can be referenced from the route part by the Content-Id. The following is an example of referencing an attachment from the route part. The bold portion indicates the CID URL schema and the Content-Id of the corresponding attachment.

-uuid:e63fe7dc-ad8a-4fb1-8f56-ce7b5841a06f
Content-Type: text/xml
 
<?xml version="1.0" ?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
  <S:Body>
    <getUserData xmlns="http://localhost">
      <in0>
        <xop:Include xmlns="http://www.w3.org/2004/08/xop/include" href="cid:39820675-44bb-4e28-9926-577bf27fa07c@jaxws.cosminexus.com"/>
      </in0>
    </getUserData>
  </S:Body>
</S:Envelope>
 
--uuid:e63fe7dc-ad8a-4fb1-8f56-ce7b5841a06f
Content-Id:<39820675-44bb-4e28-9926-577bf27fa07c@jaxws.cosminexus.com>
Content-Type: image/jpeg
Content-Transfer-Encoding: binary
 
[attached data]
--e63fe7dc-ad8a-4fb1-8f56-ce7b5841a06f--

(a) Format of the XOP information set

The format of the XOP information set defined in the SOAP body of the route part is as follows:

"<xop: Include href=" + CID URL-schema + "/>"

(b) Mapping based on the data size of the attachments in MTOM/XOP specification format

The method of mapping the attachments in MTOM/XOP specification format to the attachment part differs according to the data size of the attachment specified in the Java type and the Java interface of the mapping source. The following table lists various mapping methods.

Table 30-10 Mapping the MTOM/XOP specification format attachments to the attachment part based on the data size

#1

Unlike the wsi:swaRef format attachments, this is the multipart that is formed only of the route part. SOAP envelopes are stored in the MIME body of the route part. No element of the argument corresponding to the SOAP body appears. The following is an example of XML mapping when the attachment data is null:

• The program that invokes the Web Service
  

  ... UserInfoService service = new UserInfoService(); UserInfo impl = service.getUserInfo(new MTOMFeature()); result = impl.getUserData( null ); ...

• SOAP messages
  

  --uuid:cbc0221b-8ee3-40a3-adc1-d5fa52a8d66e Content-Id: <rootpart*cbc0221b-8ee3-40a3-adc1-d5fa52a8d66e@jaxws.cosminexus.com> Content-Type: application/xop+xml;charset=utf-8;type="text/xml" Content-Transfer-Encoding: binary <?xml version="1.0" ?> <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> <S:Body> <ns2:getUserData xmlns:ns2="http://localhost"> </ns2:getUserData> </S:Body> </S:Envelope> --uuid:cbc0221b-8ee3-40a3-adc1-d5fa52a8d66e--

#2

This is a multipart that is formed of the attachment part that has no route part and data (MIME body is empty). If multiple attachment data is specified in the Java interface, the attachment parts will also be multiple.

#3

This is a multipart that is formed of a route part and an attachment part. If multiple attachment data is specified in the Java interface, the attachment parts will also be multiple.