[ https://issues.apache.org/jira/browse/CXF-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang resolved CXF-8112. ------------------------------- Resolution: Fixed > Default WebApplicationExceptionMapper is preferred over custom one but > Documentation states opposite > ---------------------------------------------------------------------------------------------------- > > Key: CXF-8112 > URL: https://issues.apache.org/jira/browse/CXF-8112 > Project: CXF > Issue Type: Bug > Components: Documentation > Affects Versions: 3.3.3 > Reporter: Daniel H. Peger > Assignee: Freeman Fang > Priority: Major > > The documentation on customizing the exception mapping in JAX-RS mentions > that custom mappers will be preferred over the default > {{WebApplicationExceptionMapper}}: > {quote}Note that the custom WebApplicationException mapper, if registered, > will be preferred to the default one.{quote} > See > https://cxf.apache.org/docs/jax-rs-basics.html#JAX-RSBasics-CustomizingdefaultWebApplicationExceptionmapper > Lately I noticed that after upgrading CXF this is not true anymore for > exception mappers that handle all kind of exceptions like > {{ExceptionMapper<Throwable>}}. > In CXF-6568 it is mentioned that a new property (actual property name seems > to be {{default.wae.mapper.least.specific}}) was introduced to restore the > previous behavior. I think this property should be mentioned on the JAX-RS > basics page, as I didn't find any other resource pointing to this possibility. -- This message was sent by Atlassian Jira (v8.3.2#803003)