MTOM/XOP message use always "text/xml" for start-info regardless of 'type' parameter of root part! -------------------------------------------------------------------------------------------------- Key: JBWS-2419 URL: https://jira.jboss.org/jira/browse/JBWS-2419 Project: JBoss Web Services Issue Type: Bug Security Level: Public(Everyone can see) Components: jbossws-native Reporter: Franz Willer Attachments: JBWS-2419_patch.txt MultipartRelatedXOPEncoder use MimeConstants.START_INFO_XOP ("text/xml" = TYPE_SOAP11) to set 'start-info' parameter. But in "XML-binary Optimized Packaging" (http://www.w3.org/TR/xop10) "4.1 MIME Multipart/Related XOP Packages" is stated that start-info must contain the value of 'type' parameter from root part: 4.1 MIME Multipart/Related XOP Packages .. The root MIME part is the root part of the XOP package, MUST be a serialization of the XOP Infoset using any W3C recommendation-level version of XML (e.g., [Extensible Markup Language (XML) 1.0 (Third Edition)], [Extensible Markup Language (XML) 1.1]), and MUST be identified with a media type of "application/xop+xml" (as defined below). The "start-info" parameter of the package's media type MUST contain the content type associated with the content's XML serialization. (i.e. it will contain the same value as the "type" parameter of the root part). .. One effect of this is, that AXIS2 clients will throw an exception because they check if the SOAP Envelope namespace (SOAP11 or SOAP12) is conform to the transport Content-Type (text/xml or application/soap+xml).

MTOM/XOP message use always "text/xml" for start-info regardless of content type associated with the content (SOAP message) --------------------------------------------------------------------------------------------------------------------------- Key: JBWS-2419 URL: https://jira.jboss.org/jira/browse/JBWS-2419 Project: JBoss Web Services Issue Type: Bug Security Level: Public(Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.5 Reporter: Franz Willer Assignee: Magesh Kumar B Fix For: jbossws-native-3.1.0 Attachments: JBWS-2419_patch.txt MultipartRelatedXOPEncoder use MimeConstants.START_INFO_XOP ("text/xml" = TYPE_SOAP11) to set 'start-info' parameter. But in "XML-binary Optimized Packaging" (http://www.w3.org/TR/xop10) "4.1 MIME Multipart/Related XOP Packages" is stated that start-info must contain the value of 'type' parameter from root part: 4.1 MIME Multipart/Related XOP Packages .. The root MIME part is the root part of the XOP package, MUST be a serialization of the XOP Infoset using any W3C recommendation-level version of XML (e.g., [Extensible Markup Language (XML) 1.0 (Third Edition)], [Extensible Markup Language (XML) 1.1]), and MUST be identified with a media type of "application/xop+xml" (as defined below). The "start-info" parameter of the package's media type MUST contain the content type associated with the content's XML serialization. (i.e. it will contain the same value as the "type" parameter of the root part). .. One effect of this is, that AXIS2 clients will throw an exception because they check if the SOAP Envelope namespace (SOAP11 or SOAP12) is conform to the transport Content-Type (text/xml or application/soap+xml).