[
https://issues.apache.org/jira/browse/CXF-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15693006#comment-15693006
]
Sergey Beryozkin commented on CXF-7119:
---------------------------------------
I've added this test in fault interceptor:
http://git-wip-us.apache.org/repos/asf/cxf/blob/c3c887a1/systests/jaxrs/src/test/java/org/apache/cxf/systest/jaxrs/CustomFaultInInterceptor.java
Note it throws ProcessingException directly which results in the test avoiding
having to go to the cause:
https://git1-us-west.apache.org/repos/asf?p=cxf.git;a=blob;f=systests/jaxrs/src/test/java/org/apache/cxf/systest/jaxrs/JAXRSClientServerBookTest.java;h=da1f0468be30b184ec581cde187216b612f07426;hb=96f64799#l2645
But the interceptor can rethrow some custom exception in which case it will be
wrapped in ProcessingException.
Message has many other properties related to the current request too,
Also note this interceptor can be added before the proxy is created via
JAXRSClientFactoryBean.
I think this issue will now need to be resolved with something like Works As
Expected or similar given that CXF already offers the loose mechanism to handle
the technical exceptions
> Introduce a JAX-RS client provider for catching technical exceptions (e.g.
> IOException)
> ---------------------------------------------------------------------------------------
>
> Key: CXF-7119
> URL: https://issues.apache.org/jira/browse/CXF-7119
> Project: CXF
> Issue Type: New Feature
> Components: JAX-RS
> Affects Versions: 3.1.3
> Reporter: Jörg Hohwiller
> Assignee: Sergey Beryozkin
> Fix For: 3.2.0, 3.1.9
>
>
> When using CXF for REST/JAX-RS service clients I quickly noticed that I need
> to tweak the error handling. My services use an ExceptionMapper that provides
> error details via JSON result payload. Hence I want to access this and render
> an exception with further details and more context information what works
> fine with ResponseExceptionMapper.
> However, when a technical error (IOException such as unkown host, connection
> refused, timeout, etc.) occurrs I only get generic errors from CXF client
> (org.apache.cxf.interceptor.Fault: Could not send Message.). This is
> undesired but unfortunately my custom ResponseExceptionMapper is never called
> for such technical errors. There seems to be no way to archive my goal with
> CXF itself. I could only wrap the client again with a custom written dynamic
> proxy to reach my goal.
> It seems that CXF hardwires this behaviour:
> https://github.com/apache/cxf/blob/master/rt/rs/client/src/main/java/org/apache/cxf/jaxrs/client/AbstractClient.java#L596
> https://github.com/apache/cxf/blob/master/core/src/main/java/org/apache/cxf/interceptor/MessageSenderInterceptor.java#L64
> It would be awesome if in such case ResponseExceptionMapper would also be
> applied so I have the chance to interfere and produce better exceptions (e.g.
> with a message containing the name of the application/microservice that could
> not be called, the URL, etc.) for my individual needs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
