]
Franz Willer updated JBWS-2419:
-------------------------------
Attachment: JBWS-2419_patch.txt
Added patch file:
Check SOAP version of SOAPMessage and get the corresponding type (text/xml or
application/soap+xml) to set 'start-info' and 'type' parameter.
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).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: