You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cxf.apache.org by "Giedrius Noreikis (JIRA)" <ji...@apache.org> on 2018/07/17 16:05:00 UTC

[jira] [Created] (CXF-7798) Mapping of SOAP Faults in Asynchronous JAX-WS Client

Giedrius Noreikis created CXF-7798:
--------------------------------------

             Summary: Mapping of SOAP Faults in Asynchronous JAX-WS Client
                 Key: CXF-7798
                 URL: https://issues.apache.org/jira/browse/CXF-7798
             Project: CXF
          Issue Type: Bug
          Components: JAX-WS Runtime
    Affects Versions: 3.2.5
            Reporter: Giedrius Noreikis


When a SOAP fault is received, asynchronous JAX-WS client throws {{ExecutionException}} with a CXF-specific {{SoapFault}} as its cause:

{code:java}
Caused by: java.util.concurrent.ExecutionException: org.apache.cxf.binding.soap.SoapFault: ...
	at org.apache.cxf.endpoint.ClientCallback.get(ClientCallback.java:147)
	at org.apache.cxf.jaxws.JaxwsResponseCallback.get(JaxwsResponseCallback.java:49)
	...
{code}

Instead, the cause of {{ExecutionException}} is supposed to contain an instance of {{javax.xml.ws.soap.SOAPFaultException}} in this case, as the mapping should be identical for both asynchronous and synchronous cases.




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)