-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.3.3
-
Fix Version/s: None
-
Component/s: Documentation
-
Labels:None
-
Estimated Complexity:Unknown
The documentation on customizing the exception mapping in JAX-RS mentions that custom mappers will be preferred over the default WebApplicationExceptionMapper:
Note that the custom WebApplicationException mapper, if registered, will be preferred to the default one.
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.