You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Andriy Redko (Jira)" <ji...@apache.org> on 2020/04/29 00:40:00 UTC
[jira] [Resolved] (CXF-8261) Exceptions being thrown in a
ClientResponseFilter are ignored
[ https://issues.apache.org/jira/browse/CXF-8261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andriy Redko resolved CXF-8261.
-------------------------------
Resolution: Fixed
> Exceptions being thrown in a ClientResponseFilter are ignored
> -------------------------------------------------------------
>
> Key: CXF-8261
> URL: https://issues.apache.org/jira/browse/CXF-8261
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Affects Versions: 3.3.6, 3.2.13
> Reporter: Matthias
> Assignee: Andriy Redko
> Priority: Major
> Fix For: 3.4.0, 3.2.14, 3.3.7
>
>
> Hi,
> I have a rest client that follows the JAX-RS specification and that is used with different implementations like Jersey, RestEasy and Apache CXF. The rest server sometimes throws a "404 Not Found" with a json body if something goes wrong. I am processing that response in a ClientResponseFilter and throwing a custom exception, but Apache CXF somehow ignores that exception and throws a NotFoundException instead. All other JAX-RS implementations (jersey, resteasy) are wrapping my exception in a ResponseProcessingException, so that I can properly access that error.
> My expectation is that Apache CXF behaves like other implementations. I am not even able to access the json body when I get an error status code. The CXF client seems to completely suppress the response body.
> You can check that issue in this repository: [https://github.com/prof-schnitzel/cxf-rest-sample]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)