cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aki Yoshida (JIRA)" <>
Subject [jira] [Commented] (CXF-4794) Soap 1.1 service returns an invalid soap fault for soap 1.2 requests
Date Mon, 04 Feb 2013 12:14:13 GMT


Aki Yoshida commented on CXF-4794:

Hi Alex,
somehow the jira plugin is not adding the rev info automatically.
here is the trunk rev

regards, aki
> Soap 1.1 service returns an invalid soap fault for soap 1.2 requests
> --------------------------------------------------------------------
>                 Key: CXF-4794
>                 URL:
>             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,
> <soap:Envelope xmlns:soap="">
>   <soap:Body>
>     <soap:Fault>
>       <faultcode xmlns:ns1="">ns1:VersionMismatch</faultcode>
>       <faultstring>A SOAP 1.2 message is not valid when sent to a SOAP 1.1 only
>     </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:

View raw message