Error handling with CXF interceptors - changing the response message

Question

I'm trying to handle errors coming from my backend. The `handleMessage()` is called if an error occurs but the content is an instance of XmlMessage. I would like to change it to my own response - just set the response code and add some message. I haven't found any proper documentation which could tell me how to do this... These axamples are for REST but I'd like to manage this thing in SOAP too. interceptor ``` public class ErrorHandlerInterceptor extends AbstractPhaseInterceptor { public ErrorHandlerInterceptor() { super(Phase.POST_LOGICAL); } @Override public void handleMessage(Message message) throws Fault { Response response = Response .status(Response.Status.BAD_REQUEST) .entity("HOW TO GET A MESSAGE FROM AN EXCEPTION IN HERE???") .build(); message.getExchange().put(Response.class, response); } } ``` context.xml ``` …

Accepted Answer

And here's the other piece of your puzzle. You're already using JAX-RS, so why not use JAX-WS as well?

This thread and this blog post cover mapping Exceptions into SOAP faults. Short and sweet:

The JAX-WS 2.0 specification demands that the exception annotated with `@WebFault` must have two constructors and one method [getter to obtain the fault information]:

```
WrapperException(String message, FaultBean faultInfo)
WrapperException(String message, FaultBean faultInfo, Throwable cause)
FaultBean getFaultInfo()
```

The WrapperException is replaced by the name of the exception, and FaultBean is replaced by the class name that implements the fault bean. The fault bean is a Java bean that contains the information of the fault and is used by the Web service client to know the cause for the fault.

And there's your mapping. Simply specify implementations of the above signatures in the context of `@WebFault` and your SOAP API should map these happily. Obviously, the links contain more details.

Error handling with CXF interceptors - changing the response message

Solution

Problem

Related problems