cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Carman (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CXF-6635) Wrong ExceptionMapper Chosen When a Hierarchy is Used
Date Fri, 09 Oct 2015 14:52:28 GMT

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

James Carman closed CXF-6635.
-----------------------------
    Resolution: Done

This issue is already fixed in 3.0.6.  I changed my test code to use 3.0.6 and it went away.
 Sweet!  Thanks and sorry for the noise.

> Wrong ExceptionMapper Chosen When a Hierarchy is Used
> -----------------------------------------------------
>
>                 Key: CXF-6635
>                 URL: https://issues.apache.org/jira/browse/CXF-6635
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 3.0.5
>            Reporter: James Carman
>
> I have an abstract superclass for all of my ExceptionMappers, since they basically all
do the same thing, they just handle different exception types.  Anyway, when I try to hit
a completely wrong URL, my ExceptionMapper is triggered as opposed to using the built-in ExceptionMapper
which would return the 404.  This can be exhibited by the following test case:
> https://github.com/jwcarman/cxf-sandbox/blob/master/jaxrs/src/test/java/com/carmanconsulting/sandbox/cxf/jaxrs/ExceptionMapperTest.java
> I'm working on a patch to CXF now.  Just  needed a JIRA number for the branch name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message