[CXF-5348] Exception mappers implementing ExceptionMapper through an abstract class are not mapped to the declared exception

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.7.7
• Fix Version/s: 3.0.0-milestone2, 2.7.10
• Component/s: JAX-RS
• Estimated Complexity: Unknown
• Assignee: Sergey Beryozkin
• Reporter: Fabien Thouny
• Created: 21/Oct/13 15:41
• Updated: 04/Sep/17 11:13
• Resolved: 31/Jan/14 18:34

Description

If we consider the following exception mapper, all Throwables will be mapped instead of only the SomeClientExceptions :

@Provider
public class SomeClientExceptionMapper extends AbstractBadRequestExceptionMapper<SomeClientException> {}

abstract class AbstractBadRequestExceptionMapper<T extends Throwable> implements ExceptionMapper<T> {

    @Override
    public Response toResponse(T exception) {
        return Response.status(Status.BAD_REQUEST).entity(exception.getMessage()).build();
    }
}

Please find attached, a sample project with some ITs showing the problem.

Issue Links

• is related to: CXF-7473 ExceptionMapper class hierarchies: incompatible ExceptionMapper selected