cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Hohwiller (JIRA) <>
Subject [jira] [Commented] (CXF-7119) Introduce a JAX-RS client provider for catching technical exceptions (e.g. IOException)
Date Wed, 23 Nov 2016 14:32:58 GMT


Jörg Hohwiller commented on CXF-7119:

You are right that ResponseExceptionMapper does not make sense for this purpose as its API
does not properly fit here.
Any kind of provider that takes a Throwable and can propduce a new Throwable or potentially
even consume it would be great.
Your Interceptor concept seems to rely on Message as input. If you would not have to consider
compatibility to jdk < 1.8 you could simply accept any Function<Throwable, Throwable>
but otherwise I suggest just to create a new interface for that purpose. It should IMHO be
decoupled from the service technology (JAX-RS, JAX-WS, etc.).

> Introduce a JAX-RS client provider for catching technical exceptions (e.g. IOException)
> ---------------------------------------------------------------------------------------
>                 Key: CXF-7119
>                 URL:
>             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:
> 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

This message was sent by Atlassian JIRA

View raw message