Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Sun, 20 Nov 2016 18:38:58 +0000 (UTC)
From: "Sergey Beryozkin (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.13016858.1477995384000.323032.1479667138666@Atlassian.JIRA>
In-Reply-To: <JIRA.13016858.1477995384000@Atlassian.JIRA>
References: <JIRA.13016858.1477995384000@Atlassian.JIRA> <JIRA.13016858.1477995384463@arcas>
Subject: [jira] [Resolved] (CXF-7119) ResponseExceptionMapper not used for
 technical exceptions (e.g. IOException)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Sun, 20 Nov 2016 18:39:00 -0000


     [ https://issues.apache.org/jira/browse/CXF-7119?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Beryozkin resolved CXF-7119.
-----------------------------------
       Resolution: Fixed
         Assignee: Sergey Beryozkin
    Fix Version/s: NeedMoreInfo

> ResponseExceptionMapper not used for technical exceptions (e.g. IOExcepti=
on)
> -------------------------------------------------------------------------=
---
>
>                 Key: CXF-7119
>                 URL: https://issues.apache.org/jira/browse/CXF-7119
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 3.1.3
>            Reporter: J=C3=B6rg Hohwiller
>            Assignee: Sergey Beryozkin
>             Fix For: NeedMoreInfo
>
>
> When using CXF for REST/JAX-RS service clients I quickly noticed that I n=
eed to tweak the error handling. My services use an ExceptionMapper that pr=
ovides error details via JSON result payload. Hence I want to access this a=
nd render an exception with further details and more context information wh=
at works fine with ResponseExceptionMapper.=20
> However, when a technical error (IOException such as unkown host, connect=
ion refused, timeout, etc.) occurrs I only get generic errors from CXF clie=
nt (org.apache.cxf.interceptor.Fault: Could not send Message.). This is und=
esired 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 dynam=
ic 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/c=
xf/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)