[
https://issues.apache.org/jira/browse/CXF-6635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14950420#comment-14950420
]
James Carman commented on CXF-6635:
-----------------------------------
Take a look at the test. It's typed to the custom exception type.
> 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)
