[ 
https://issues.apache.org/jira/browse/CXF-8452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325275#comment-17325275
 ] 

Freeman Yue Fang commented on CXF-8452:
---------------------------------------

Hi [~vevasant],

Thanks for the reproducer, and I got your point now.

In this case I think you can simply throw an exception at the end of 
SoapOutboundMessageInterceptor, this will stop the interceptor chain 
immediately. And in your main you can catch this exception and log it, and keep 
manipulating the soap message you revised.

I just attached 
[myTestCXF01.tar|https://issues.apache.org/jira/secure/attachment/13024301/myTestCXF01.tar]
 which is based on your project FYI.

Hope this helps!
Freeman

> Upgrade of cxf to version greater than 3.2.2 resulting in SOAPFaultException
> ----------------------------------------------------------------------------
>
>                 Key: CXF-8452
>                 URL: https://issues.apache.org/jira/browse/CXF-8452
>             Project: CXF
>          Issue Type: Test
>            Reporter: Veeksha A V
>            Assignee: Freeman Yue Fang
>            Priority: Major
>         Attachments: SoapOutboundMessageInterceptor.java, 
> SoapOutboundMessageInterceptor.java, TestClient.java, TestClient.java, 
> TestClient.java, myTestCXF01.tar, myTestCXF01.zip, soap-bindings.jar
>
>
> We are trying to upgrade apache cxf in our components to 3.4.1 , when 
> upgraded we are ending up with runtime exception below : 
> ```
> javax.xml.ws.soap.SOAPFaultException, message: Response message did not 
> contain proper response data.
> Caused by: org.apache.cxf.endpoint.ClientImpl$IllegalEmptyResponseException: 
> Response message did not contain proper response data.
> ```
> Got to know this is because of this checkin: 
> [https://github.com/apache/cxf/commit/1396f046333108ec0e7819bf4de154505ff4564c,|https://github.com/apache/cxf/commit/1396f046333108ec0e7819bf4de154505ff4564c]
> Needed help in understanding why is it so and how can we overcome it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to