[
https://issues.apache.org/jira/browse/CXF-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908621#action_12908621
]
Freeman Fang commented on CXF-2990:
-----------------------------------
This error comes from that for async invocation, in ClientImpl.processResult()
method, currently code like
{code}
// Check to see if there is a Fault from the outgoing chain
Exception ex = message.getContent(Exception.class);
if (ex != null) {
...
throw ex;
}
{code}
Actually here message is InBoundMessage, and the ex here is a incoming soap
fault, we shouldn't get/throw ex like this at this stage, as throw ex too early
we get no chance to set context content for soap fault incoming message.
we should bypass this check if message is InBoundMessage
> Response Context should not be empty even with a SOAP fault message when use
> async invoke
> ------------------------------------------------------------------------------------------
>
> Key: CXF-2990
> URL: https://issues.apache.org/jira/browse/CXF-2990
> Project: CXF
> Issue Type: Bug
> Reporter: Freeman Fang
> Assignee: Freeman Fang
> Fix For: 2.3, 2.2.11
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
