Spring Integration中的错误处理期间的MessageTransformation异常

Question

I have a http inboundgateway and defined an error channel to the gateway .

<int-http:inbound-gateway 
    request-channel="requestChannel"  reply-channel="replyChannel" 
        supported-methods="POST" request-payload-type="com.test.RequestWsDTO"
    path="/trips/modify" error-channel="errorChannel" >
    <int-http:request-mapping consumes="application/json" produces="application/json" />
</int-http:inbound-gateway>

From the gateway , it goes to a transformer to transform the message to an appropriate request for ws outboundgateway

<int:transformer id="segmentCancelTransformer" ref="segmentCancelTransformerBean" input-channel="segmentCancelChannel"
             method="transform" output-channel="rcsChannel"/>
    <beans:bean id="segmentCancelTransformerBean" class="com.test.SegmentCancelRequestTransformer" />

I throw a runtime exception from the Transformer .

I have defined an service activator to handle the exception

   <int:service-activator input-channel="errorChannel" ref="exceptionhandler" method="createErrorResponse"/>
<beans:bean id="exceptionTransformer" class="com.test.ExceptionHandler" />

In the ExceptionHandler class , I am handling the exception like

public  ErrorDTO createErrorResponse(ErrorMessage msg) {
        System.out.println("Exception occured "+msg.getPayload());
        ErrorDTO dto=new ErrorDTO ();
      ......................

msg.getPayload() is showing the exception to be of "org.springframework.integration.transformer.MessageTransformationException"

Exception message stacktrace:

Exception occured org.springframework.integration.transformer.MessageTransformationException: Failed to transform Message; nested exception is org.springframework.messaging.MessageHandlingException: nested exception

What am i doing wrong here ?

Answer 1

That's really correct and also useful. First, you deal with messaging where the loosely-coupling is the first of principles between components. Another advantage is the failedMessage set to the property of the MessagingException which you can use to determine the problem.

Since the error maybe from another thread, it's hard to determine what's wrong by just a custom exception. Anyway you always can find your own cause in the stack trace.