What would be the HTTP content-type header when a message is optimized using MTOM ? (Choose one)

What would be the HTTP content-type header when a message is optimized using MTOM ? (Choose one)

What would be the HTTP content-type header when a message is optimized using MTOM ? (Choose one)

A.
multipart/related

B.
text/xml

C.
application/soap+xml

D.
application/xop+xml



Leave a Reply 2

Your email address will not be published. Required fields are marked *


coco

coco

When MTOM/XOP is used to optimize a SOAP message, it is serialized into a MIME Multipart/Related message using XOP processing. The base64Binary data is extracted from the SOAP message and packaged as separate binary attachments within the MIME message, in a similar manner to e-mail attachments.
The size of the base64Binary data is significantly reduced because the attachments are encoded in binary format. The XML in the SOAP message is then converted to XOP format by replacing the base64Binary data with a special element that references the relevant MIME attachment using a URI.

The modified SOAP message is called the XOP document, and forms the root document within the message. The XOP document and binary attachments together form the XOP package. When applied to the SOAP MTOM specification, the XOP package is a MIME message in MTOM format.

The root document is identified by referencing its Content-ID in the overall content-type header of the MIME message. Here is an example of a content-type header:

Content-Type: Multipart/Related; boundary=MIME_boundary;
type=”application/soap+xml”; start=””

http://www.ibm.com/support/knowledgecenter/SSGMCP_5.2.0/com.ibm.cics.ts.webservices.doc/mtomxop/dfhws_attachments_and_SOAP.html

A is correct

Mohamed Fayek Saber

Mohamed Fayek Saber

http://www.mkyong.com/webservices/jax-ws/jax-ws-attachment-with-mtom/

HTTP/1.1 200 OK
Transfer-encoding: chunked
Content-type: multipart/related;
start=””;
type=”application/xop+xml”;
boundary=”uuid:c73c9ce8-6e02-40ce-9f68-064e18843428″;
start-info=”text/xml”

–uuid:c73c9ce8-6e02-40ce-9f68-064e18843428
Content-Id:
Content-Type: application/xop+xml;charset=utf-8;type=”text/xml”
Content-Transfer-Encoding: binary