[
https://issues.jboss.org/browse/WFLY-4137?page=com.atlassian.jira.plugin....
]
Tomas Hofman updated WFLY-4137:
-------------------------------
Description:
Clone of EAP6 issue
https://bugzilla.redhat.com/show_bug.cgi?id=1167348 - WF is also
susceptible.
Description of problem:
There is wrong content type (text/xml) in multipart SOAPMessage when sending it using
javax.xml.soap API. So target system is unable to parse it.
How reproducible:
always
Additional info:
It's also wrong in EAP 6.2.
EAP 6.1 is OK.
There is a patch attached in BZ-1167348 for JBossWS CXF 4.3.3. The same fix should be also
applied to JBossWS CXF 5.0.0 which is used by Wildfly.
was:
Clone of EAP6 issue
https://bugzilla.redhat.com/show_bug.cgi?id=1167348 - WF is also
susceptible.
Description of problem:
There is wrong content type (text/xml) in multipart SOAPMessage when sending it using
javax.xml.soap API. So target system is unable to parse it.
How reproducible:
always
Additional info:
It's also wrong in EAP 6.2.
EAP 6.1 is OK.
There is a patch attached in BZ-1167348 for JBoss CXF 4.3.3. The same fix should be also
applied to JBoss CXF 5.0.0 which is used by Wildfly.
Wrong content type (text/xml) in outgoing multipart SOAPMessage
(expected multipart/related; ...)
-------------------------------------------------------------------------------------------------
Key: WFLY-4137
URL:
https://issues.jboss.org/browse/WFLY-4137
Project: WildFly
Issue Type: Bug
Components: Web Services
Affects Versions: 9.0.0.Alpha1
Reporter: Tomas Hofman
Assignee: Tomas Hofman
Clone of EAP6 issue
https://bugzilla.redhat.com/show_bug.cgi?id=1167348 - WF is also
susceptible.
Description of problem:
There is wrong content type (text/xml) in multipart SOAPMessage when sending it using
javax.xml.soap API. So target system is unable to parse it.
How reproducible:
always
Additional info:
It's also wrong in EAP 6.2.
EAP 6.1 is OK.
There is a patch attached in BZ-1167348 for JBossWS CXF 4.3.3. The same fix should be
also applied to JBossWS CXF 5.0.0 which is used by Wildfly.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)