[CXF-7473] ExceptionMapper class hierarchies: incompatible ExceptionMapper selected

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1.11, 3.1.12
• Fix Version/s: 3.2.2, 3.1.15
• Component/s: JAX-RS
• Estimated Complexity: Unknown
• Assignee: Sergey Beryozkin
• Reporter: Jocelyn Lepage
• Created: 14/Aug/17 14:47
• Updated: 07/Feb/18 14:52
• Resolved: 01/Feb/18 13:24

Description

CXF seems to select an incompatible ExceptionMapper when using class hierarchies.

More precisely, if I define an abstract exception class like following:

@Provider
public abstract class AbstractExceptionMapper<E extends Throwable> implements ExceptionMapper<E> {
...

Then I define a concrete one for IllegalArgumentExceptions:

public class IllegalArgumentExceptionMapper extends AbstractExceptionMapper<IllegalArgumentException> {
...

IllegalArgumentExceptionMapper will then be selected even for RuntimeException subtypes unrelated to IllegalArgumentExceptions.

See minimal project showing the problem here

Similar (if not same) problem seems to have been reported via CXF-6635, but I do see this with 3.1.11 and 3.1.12.

Thx!

Issue Links

• relates to: CXF-6635 Wrong ExceptionMapper Chosen When a Hierarchy is Used
• relates to: CXF-5348 Exception mappers implementing ExceptionMapper through an abstract class are not mapped to the declared exception
• relates to: CXF-6067 ProviderFactory fails to analyze generic types correctly with some class hierachies