[
https://issues.apache.org/jira/browse/CXF-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aki Yoshida resolved CXF-4794.
------------------------------
Resolution: Fixed
Fix Version/s: 2.5.10
2.6.7
2.7.4
2.8.0
changed
- the server side so that it returns a valid soap fault 1.1. in this case.
- the client side so that it doesn't get an unexpected NPE even if the
returned fault is invalid/inconsistent.
> Soap 1.1 service returns an invalid soap fault for soap 1.2 requests
> --------------------------------------------------------------------
>
> Key: CXF-4794
> URL: https://issues.apache.org/jira/browse/CXF-4794
> Project: CXF
> Issue Type: Bug
> Components: Soap Binding
> Affects Versions: 2.7.2
> Reporter: Aki Yoshida
> Assignee: Aki Yoshida
> Fix For: 2.8.0, 2.7.4, 2.6.7, 2.5.10
>
>
> The soap 1.1 endpoint (i.e., soap 1.2 binding not enabled) is supposed to
> returns a soap fault when a soap 1.2 message is received. The fault is
> correctly raised, however, the returned fault message is inconsistent and has
> the soap 1.2 fault containing the soap 1.1 fault content, as
> <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope";>
> <soap:Body>
> <soap:Fault>
> <faultcode
> xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/";>ns1:VersionMismatch</faultcode>
> <faultstring>A SOAP 1.2 message is not valid when sent to a SOAP 1.1
> only endpoint.</faultstring>
> </soap:Fault>
> </soap:Body>
> </soap:Envelope>
> This will lead to problems at most soap clients (including CXF which gets an
> NPE), as the fault code is not found at the expected element.
> We can fix this by returning either the soap 1.1 fault or the soap 1.2 fault.
> The client that sent the soap 1.2 request message obviously understands both
> soap 1.2 and 1.1, it is not clear whether the service must return the soap
> 1.1 message or may return the message of the same version as the request
> message, in this case, the soap 1.2 message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
