0

我一直在互联网上搜索并尝试了许多不同的方法,但我无法让它发挥作用。

我想要的是捕获从出站端抛出的异常,例如一些验证,当它们没有成功通过时,它们应该向发件人返回一个异常。我不知道是否可以不使用 DirectChannel 从服务器发送请求。

我希望有一个人可以帮助我。

在下面的代码中,我向您展示了我的 SI 配置,其中使用 SPEL 表达式“checkRemoteOutputHeaders”的过滤器在执行时会引发异常。

<int:channel id="requestChannelSb">
    <int:interceptors>
        <int:wire-tap channel="timeStampCalllogger" />
    </int:interceptors>
</int:channel>

<task:executor id="threadPoolTaskExecutor" pool-size="10" queue-capacity="100" rejection-policy="DISCARD_OLDEST" />

<bean id="taskExecutor" class="org.springframework.integration.util.ErrorHandlingTaskExecutor">
    <constructor-arg name="executor" ref="threadPoolTaskExecutor"/>
    <constructor-arg name="errorHandler">
        <bean class="org.springframework.integration.channel.MessagePublishingErrorHandler">
            <property name="defaultErrorChannel" ref="errorChannel"/>
        </bean>
    </constructor-arg>
</bean>

<int:channel id="gatewayChannelSb">
    <int:dispatcher task-executor="taskExecutor" failover="false"/>

    <int:interceptors>
        <int:wire-tap channel="timeStampInitlogger" />
    </int:interceptors>
</int:channel>
<int:channel id="responseChannelSb">
    <int:interceptors>
        <int:wire-tap channel="timeStampEndlogger" />
    </int:interceptors>
</int:channel>
<int:channel id="errorChannel">
    <int:interceptors>
        <int:wire-tap channel="errorlogger"/>
    </int:interceptors>
</int:channel>


<int-http:outbound-gateway request-channel="requestChannelSb"
    url="{urlVar}" http-method="POST"
    extract-request-payload="true"
    expected-response-type="java.lang.String"
    charset="UTF-8"
    header-mapper="headerMapper"
    reply-channel="responseChannelSb"
    request-timeout="60000">

    <int-http:uri-variable name="urlVar" expression="T(gnf.servicebroker.util.Utils).getUrl(headers)" />

</int-http:outbound-gateway>

<int:chain input-channel="responseChannelSb">
    <int:header-enricher>
        <int:header name="#{T(gnf.servicebroker.util.Constantes$HEADERS).BEAN}" expression="headers[T(gnf.servicebroker.util.Constantes$HEADERS).BEAN]"/>
    </int:header-enricher>
    <int:transformer ref="customJsonToObjectTransformer"/>
</int:chain>


<int:chain id="chain" input-channel="gatewayChannelSb" output-channel="requestChannelSb">

    <int:header-enricher>
        <int:error-channel ref="errorChannel" overwrite="true"/>
        <int:header name="#{T(gnf.servicebroker.util.Constantes$HEADERS).REQUEST_ID}" expression="headers[T(gnf.servicebroker.util.Constantes$HEADERS).ID].toString()"/>
    </int:header-enricher>

    <int:filter expression="T(gnf.servicebroker.util.Utils).checkRemoteOutputHeaders(headers)" discard-channel="errorChannel" />

    <int:header-enricher>
        <int:header name="#{T(gnf.servicebroker.util.Constantes$HEADERS).CONTENT_TYPE}" value="text/x-json" />
        <int:header name="#{T(gnf.servicebroker.util.Constantes$HEADERS).ACCEPT}" value="text/x-json" />
        <int:header name="#{T(gnf.servicebroker.util.Constantes$HEADERS).BEAN}" expression="T(gnf.servicebroker.util.Utils).getPayloadCanonicalClassName(payload)" />
        <int:header name="#{T(gnf.servicebroker.util.Constantes$HEADERS).SECURITY_USER}" expression="T(gnf.servicebroker.util.Utils).getSecurityUser()"/>
        <int:header name="#{T(gnf.servicebroker.util.Constantes$HEADERS).TARGET}" expression="T(gnf.servicebroker.util.Utils).getTargetUrl()"/>
    </int:header-enricher>

    <int:object-to-json-transformer object-mapper="jsonObjectMapper"/>
</int:chain>



<!-- Logging channels -->

<int:logging-channel-adapter id="timeStampInitlogger" level="INFO" expression="'Inicio de la peticion: '.concat(T(gnf.servicebroker.util.Utils).getRequestInfoTrace(headers))"/>
<int:logging-channel-adapter id="timeStampCalllogger" level="INFO" expression="'Envio de la peticion: '.concat(T(gnf.servicebroker.util.Utils).getRequestInfoTrace(headers))"/>
<int:logging-channel-adapter id="timeStampEndlogger" level="INFO" expression="'Final de la peticion: '.concat(T(gnf.servicebroker.util.Utils).getRequestInfoTrace(headers))"/>
<int:logging-channel-adapter id="destinationCalllogger" level="INFO" expression="'Destino peticion: '.concat(headers[T(gnf.servicebroker.util.Constantes$HEADERS).SUBSYSTEM])"/>

<int:logging-channel-adapter id="errorlogger" level="ERROR" expression="'ERROR: '.concat(T(gnf.servicebroker.util.Utils).getRequestInfoTrace(headers))"/>

<!-- End Logging channels -->


<int:chain input-channel="errorChannel" output-channel="responseChannelSb">
    <int:transformer ref="messageHandlingExceptionTransformer"/>
</int:chain>

在下面的代码中,我向您展示了转换器“messageHandlingExceptionTransformer”,它将 MessaggingException 转换为 ServiceException(自定义异常):

    @Transformer
public Message<ServiceException> transform(ErrorMessage message){

    LOGGER.debug("INIT - transform(message=" + message + ")");

    MessagingException messageException = (MessagingException) message.getPayload();

    ServiceException serviceEx = new ServiceException(messageException.getMessage(), messageException.getCause());

    Message<?> originalMsg = messageException.getFailedMessage();

    Message<ServiceException> transformedObj = MessageBuilder.withPayload(serviceEx).copyHeaders(originalMsg.getHeaders()).build();


    LOGGER.debug("END - transform=" + transformedObj);

    return transformedObj;
}

另一个转换器“customJsonToObjectTransformer”只是将字符串负载(JSON)转换为 Java 对象并返回,但如果负载不是字符串,例如异常,则直接返回。

提前说。

4

1 回答 1

0

终于找到了调用者在出站生命周期中没有收到抛出的异常的原因。

我只是一个配置问题,因为在其他 XML 文件中我有网关定义,它指示其错误通道与出站配置中定义的通道相同。所以它产生了一个循环的调用链,因为在出​​站时,异常的ErrorMessage在errorChannel中一次又一次在网关的error-channel中进行管理,这是相同的,所以请求再次进入链中管理errorChannel,最后它在没有通知调用者的情况下失败。

<int:gateway id="gcccSearchServiceRequestByCodeServiceSb" 
    service-interface="gnf.servicebroker.gps.atencioncliente.atcomercializadora.servicerequest.service.GcccSearchServiceRequestByCodeServiceISb" 
    default-request-channel="gatewayChannelSb"
    error-channel="errorChannel">
    <int:method name="gcccSearchServiceRequestByIdSr">
        <int:header name="Method" value="gcccSearchServiceRequestByIdSr"/>
        <int:header name="Module" value="atencioncliente"/>
        <int:header name="Service" value="gnf.servicebroker.gps.atencioncliente.atcomercializadora.servicerequest.service.GcccSearchServiceRequestByCodeServiceISb"/>
        <int:header name="SubSystem" value="atec-web"/>
    </int:method>
</int:gateway>

注意error-channel属性,它与出站配置中定义的错误通道具有相同的值,因此删除此属性调用者可以捕获异常:

<int:gateway id="gcccSearchServiceRequestByCodeServiceSb" 
    service-interface="gnf.servicebroker.gps.atencioncliente.atcomercializadora.servicerequest.service.GcccSearchServiceRequestByCodeServiceISb" 
    default-request-channel="gatewayChannelSb">
    <int:method name="gcccSearchServiceRequestByIdSr">
        <int:header name="Method" value="gcccSearchServiceRequestByIdSr"/>
        <int:header name="Module" value="atencioncliente"/>
        <int:header name="Service" value="gnf.servicebroker.gps.atencioncliente.atcomercializadora.servicerequest.service.GcccSearchServiceRequestByCodeServiceISb"/>
        <int:header name="SubSystem" value="atec-web"/>
    </int:method>
</int:gateway>

我希望它对任何人都有帮助。

谢谢!!!

于 2013-10-07T11:38:37.093 回答