CODEWITHSUNDEEP
javarestsoaperror-handlingcxf
user219882
user219882

Reputation: 15834

Error handling with CXF interceptors - changing the response message

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<Message> {

    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

<bean id="errorHandlerInterceptor"
    class="cz.cvut.fit.wst.server.interceptor.ErrorHandlerInterceptor" />

<jaxrs:server address="/rest/">
    <jaxrs:serviceBeans>
        <ref bean="restService" />
    </jaxrs:serviceBeans>
    <jaxrs:outFaultInterceptors>
        <ref bean="errorHandlerInterceptor" />
    </jaxrs:outFaultInterceptors>
</jaxrs:server>

Upvotes: 8

Views: 29787

Answers (2)

MrGomez
MrGomez

Reputation: 23886

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.

Upvotes: 5

mjwenk
mjwenk

Reputation: 439

If you're using JAX-RS, why not setup an exception mapper, and then use that mapper to handle the response.

A simple example: 

@Provider
@Produces(MediaType.APPLICATION_JSON)
public class MyExceptionMapper implements
        ExceptionMapper<MyException> {

    @Override
    public Response toResponse(MyException e) {
        return Response.status(Status.NOT_FOUND).build();
    }

}

Then you would need to register the provider in the jaxrs serve by adding: 

<jaxrs:providers>
    <bean class="com.blah.blah.blah.blah.MyExceptionMapper"/>  
</jaxrs:providers>

in the server config in the context. With that you have full access to the exception, and can get whatever you want from it.

Upvotes: 15

Related Questions