[CXF-4969] ExceptionMapper not used for exception in resource setter

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6.7
• Fix Version/s: 2.6.8, 2.7.5, 3.0.0-milestone1
• Component/s: JAX-RS

Environment

tomee-1.6.0-SNAPSHOT

• Estimated Complexity: Unknown
• Assignee: Sergey Beryozkin
• Reporter: Antoine Reilles
• Created: 16/Apr/13 16:41
• Updated: 14/Aug/13 15:50
• Resolved: 17/Apr/13 21:22

Description

I'm trying to use the cxf extension that allows to map exceptions to reponses. The issue I have is that exceptions raised in setXX methods annontated with @PathParam for example are caught and produce an internal server error. This prevents from performing usefull parameter validation from the setter methods, where they could benefit to all services.

Attached in a sample application that defines a custom mapper, and raises exceptions either in a setter or a service method.

Once deployed, I do get for:

http://localhost/testexceptions/a/b/fail_in_inject

where the exception is raised at the setter level an HTTP 500 response, with entity

<ns1:XMLFault 
    xmlns:ns1="http://cxf.apache.org/bindings/xformat">
    <ns1:faultstring 
        xmlns:ns1="http://cxf.apache.org/bindings/xformat">javax.ws.rs.WebApplicationException
    </ns1:faultstring>
</ns1:XMLFault>

and a stack in the server logs, when

http://localhost/testexceptions/a/b/fail_in_serve

where the exception is raised at service level correctly returns HTTP 400

One sould be able to use the setter methods (or the resource constructor) to perform parameters validation, and property return errors.

Tested with tomee 1.6.0, which ships with cxf-2.6.7