![[Contents]](FIGURE/CONTENT.GIF)
uCosminexus Application Server, Web Service Development Guide
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
In a non-wrapper style WSDL, to specify MIME type in the xsd:base64Binary type by using an attachment in the MTOM/XOP specification format, do not use the xsd:base64Binary type for the type attribute of the xsd:element element that is referenced from the wsdl:part element. To specify MIME type as the xsd:base64Binary type, use compound type as the type attribute of the xsd:element element that is referenced from the wsdl:part element, and specify the xsd:base64Binary type in the xsd:element element of the said compound type and attach the xmime:expectedContentTypes attribute.
The xop:Include element appears in the SOAP messages of attachments in the MTOM/XOP specification format and links the route part and attachment part. Hence, you cannot use the xop:Include element in the WSDL schema declaration. Behavior is not guaranteed if the xop:Include element is used in the WSDL schema declaration.
All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd.