[
https://issues.apache.org/jira/browse/CXF-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12862595#action_12862595
]
Freeman Fang commented on CXF-2780:
-----------------------------------
Hi,
Actually this issue would occur across several interceptors which need open
underlying transport connection, not only SoapOutEndingInterceptor. Instead of
fix such issue in several interceptors, we'd like to fix it from one point to
avoid too invasive, we check exception from ClientImpl and set it as SERVER
fault code if necessary
Freeman
> Wrong soap fault code thrown on network connection failure
> ----------------------------------------------------------
>
> Key: CXF-2780
> URL: https://issues.apache.org/jira/browse/CXF-2780
> Project: CXF
> Issue Type: Bug
> Components: Soap Binding
> Affects Versions: 2.2
> Environment: Windows XP
> Reporter: Tomasz Olszewski
> Assignee: Freeman Fang
>
> When a webservice call fails due to a network failure (for example when the
> server is down and no connection can be made) CXF throws SoapFault with
> client fault code. This violates the following rule:
> "The Client class of errors indicate that the message was incorrectly formed
> or did not contain the appropriate information in order to succeed. For
> example, the message could lack the proper authentication or payment
> information. It is generally an indication that the message should not be
> resent without change."
> (http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383510)
> Exception is thrown in the following
> place:http://fisheye6.atlassian.com/browse/cxf/branches/2.2.x-fixes/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/interceptor/SoapOutInterceptor.java?r=920584#l285.
> I believe that it should be enough and safe to change
> "soapVersion.getSender()" in the linked code to "soapVersion.getReceiver()".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
