[CXF-6957] JAX-RS: ExceptionMapper not called for Fault

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1.6
• Fix Version/s: 3.0.10, 3.1.7, 3.2.0
• Component/s: JAX-RS
• Estimated Complexity: Unknown
• Assignee: Sergey Beryozkin
• Reporter: Philipp Förmer
• Created: 01/Jul/16 07:44
• Updated: 14/Oct/16 14:10
• Resolved: 01/Jul/16 11:41

Description

Hi,

let service be a cxf jax-rs based service which uses a cxf based soap proxy client to communicate with a soap service. If the cxf soap proxy client throws a org.apache.cxf.binding.soap.SoapFault, then the SoapFault is not delegated to the jax-rs ExceptionMapper chain, which is for me an unexpected behaviour.

As far as I can see this is caused by:

org.apache.cxf.service.invoker.AbstractInvoker.invoke(...), L: 123

• Rethrows exception directly without wrapping it into a fault, if exception is of type org.apache.cxf.interceptor.Fault. SoapFault is a subclass of Fault.

org.apache.cxf.jaxrs.JAXRSInvoker.handleFault, L:329

• Passes the cause of the fault to ExceptionUtils.convertFaultToResponse. The cause of the cxf SoapFault is null!

org.apache.cxf.jaxrs.utils.ExceptionUtils.convertFaultToResponse, L.65:

• Is called with null "ex" parameter and immediatley returns with null, so no exception mapper gets involved.

Thank you for your support and great project,
Philipp