You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel H. Peger (Jira)" <ji...@apache.org> on 2019/09/11 08:53:00 UTC
[jira] [Updated] (CXF-8112) Default WebApplicationExceptionMapper
is preferred over custom ones but Documentation states oposite
[ https://issues.apache.org/jira/browse/CXF-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel H. Peger updated CXF-8112:
---------------------------------
Summary: Default WebApplicationExceptionMapper is preferred over custom ones but Documentation states oposite (was: Default WebApplicationExceptionMapper is prefferred over custom ones but Documentation states oposite)
> Default WebApplicationExceptionMapper is preferred over custom ones but Documentation states oposite
> ----------------------------------------------------------------------------------------------------
>
> 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
> 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 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)