Question

我对Mule 3.3.1 CE中的Web服务有疑问。我有一个Web服务，它公开了三个操作和一个实现这些操作的类。这些操作可以返回结果（肯定）或异常（AuthExeception，ValidateExeception等）。感谢SOAP Mule Component，当我提出Java异常时，框架能够在SOAP Fault中编组java异常，但是如果我想要将SOAP Fault返回给客户端并使用Mule中的异常策略处理异常（即发送电子邮件），骡子行为不是我怎么能期望的。换句话说，当我举起一个AuthException时，流控制传递给定义的异常策略，我不再能够将SOAP Fault（AuthException）发送回客户端。

问题是：我如何发回SOAP响应并处理异常策略？

下面是一段mule xml文件，其中只使用Logger组件实现了异常策略：

<flow name="esb_consignmentFlow1" doc:name="esb_consignmentFlow1">
        <http:inbound-endpoint exchange-pattern="request-response" host="${conn.host}" port="8081" doc:name="HTTP" path="sgb/consignment" />
        <cxf:jaxws-service doc:name="Process SOAP Request" serviceClass="com.suzuki.sales.webservice.ProcessTriggerPortType"/>
        <component class="it.aizoon.suzuki.service.implementation.TriggerConsignmentOperationsImplementation" doc:name="triggerConsignmentOperationsImpl"/>
        <catch-exception-strategy doc:name="Catch Exception Strategy">
            <flow-ref name="ErrorHandling" doc:name="Flow Reference"/>
        </catch-exception-strategy>
</flow>

<flow name="ErrorHandling" doc:name="ErrorHandling" >
        <logger level="INFO" doc:name="Logger"/>
</flow>

我已经阅读了有关处理策略的内容，但我不知道这是否正确。非常感谢你的帮助。

Answer 1

下面是我的flow.xml

<?xml version="1.0" encoding="UTF-8"?>

<mule xmlns:smtp="http://www.mulesoft.org/schema/mule/smtp" xmlns:vm="http://www.mulesoft.org/schema/mule/vm" xmlns:cxf="http://www.mulesoft.org/schema/mule/cxf"   xmlns:context="http://www.springframework.org/schema/context" 
        xmlns:http="http://www.mulesoft.org/schema/mule/http" 
        xmlns="http://www.mulesoft.org/schema/mule/core" 
        xmlns:doc="http://www.mulesoft.org/schema/mule/documentation" xmlns:spring="http://www.springframework.org/schema/beans" version="CE-3.3.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="
http://www.mulesoft.org/schema/mule/vm http://www.mulesoft.org/schema/mule/vm/current/mule-vm.xsd 
http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd 
http://www.mulesoft.org/schema/mule/cxf http://www.mulesoft.org/schema/mule/cxf/current/mule-cxf.xsd 
http://www.mulesoft.org/schema/mule/smtp http://www.mulesoft.org/schema/mule/smtp/current/mule-smtp.xsd 
http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-current.xsd 
http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd ">
    <spring:beans>
        <spring:bean id="consignmentProperty" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
            <!-- In questo modo riesco a definire un file di property esterno che non è in una locazione hard-coded -->
            <spring:property name="ignoreUnresolvablePlaceholders" value="true"/>
            <spring:property name="locations">
                <spring:list>
                    <spring:value>classpath:esb_consignment.properties</spring:value>
                    <spring:value>classpath:connections.properties</spring:value>
                    <spring:value>classpath:email.properties</spring:value>
                    <!-- L'ultimo nella lista è il più generico perché sovrascrive le properties -->
                </spring:list>
            </spring:property>
        </spring:bean>
        <spring:bean id="outfaultInterceptor" class="it.aizoon.suzuki.service.interceptors.CustomSoapFaultOutInterceptor">
            <spring:property name="outputQueue" value="ErrorHandler"/>
        </spring:bean>
    </spring:beans>

    <flow name="TriggerConsignmentInterceptorService" doc:name="TriggerConsignmentInterceptorService">
        <http:inbound-endpoint exchange-pattern="request-response" host="${conn.host}" port="${conn.port}" doc:name="HTTP" path="sgb/consignment" />
        <cxf:jaxws-service doc:name="Process SOAP Request" serviceClass="com.suzuki.sales.webservice.ProcessTriggerPortType">
            <cxf:outFaultInterceptors>
                <spring:ref bean="outfaultInterceptor"/>
            </cxf:outFaultInterceptors>        
        </cxf:jaxws-service>
        <component class="it.aizoon.suzuki.service.implementation.TriggerConsignmentOperationsImplementation" doc:name="triggerConsignmentOperationsImpl"/>
    </flow>
    <flow name="ErrorHandler" doc:name="ErrorHandler">
        <vm:inbound-endpoint exchange-pattern="one-way" path="ErrorHandler" doc:name="Error Handler"/>
        <logger message="PAYLOAD: #[message.payload]" level="INFO" doc:name="Payload"/>
        <set-payload value="Tipo di Eccezione: #[message.payload]" doc:name="Set Payload"/>
        <smtp:outbound-endpoint host="${smtp.host}"
                                from="${email.fromAddress}"
                                to="${email.toAddress}" 
                                subject="${email.subject}" 
                                responseTimeout="10000" 
                                doc:name="Email Notification"/>
        <logger message="EMAIL SENT" level="INFO" doc:name="Result"/>
        <catch-exception-strategy doc:name="Catch Exception Strategy">
            <logger message="ERRORE INVIO EMAIL" level="INFO" doc:name="Logger"/>
        </catch-exception-strategy>
    </flow>

</mule>

下面是处理SOAP响应和异常策略的拦截器

package it.aizoon.suzuki.service.interceptors;

import javax.xml.bind.UnmarshalException;
import org.apache.cxf.interceptor.Fault;
import org.apache.cxf.message.Message;
import org.apache.cxf.phase.AbstractPhaseInterceptor;
import org.apache.cxf.phase.Phase;
import org.mule.DefaultMuleMessage;
import org.mule.api.MuleContext;
import org.mule.api.MuleEvent;
import org.mule.api.MuleException;
import org.mule.api.client.MuleClient;
import org.mule.api.context.MuleContextAware;
import org.mule.module.cxf.CxfConstants;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

import com.suzuki.sales.webservice.AuthenticationFailedException;
import com.suzuki.sales.webservice.ValidationFailedException;

public class CustomSoapFaultOutInterceptor extends AbstractPhaseInterceptor implements MuleContextAware{

    private static final Logger logger = LoggerFactory.getLogger(CustomSoapFaultOutInterceptor.class);

    private String outputQueue;
    private MuleContext context;


    public CustomSoapFaultOutInterceptor() {
        // TODO Auto-generated constructor stub
        super(Phase.MARSHAL);
    }

    @Override
    public void setMuleContext(MuleContext context) {
        // TODO Auto-generated method stub
        this.context = context;
    }

    @Override
    public void handleMessage(Message message) throws Fault {
        // TODO Auto-generated method stub
        MuleClient client = context.getClient();
        MuleEvent event = (MuleEvent) message.getExchange().get(CxfConstants.MULE_EVENT);
        DefaultMuleMessage muleMessage = (DefaultMuleMessage) event.getMessage();

        Throwable genericExec = message.getContent(Exception.class).getCause();
        Throwable exception = null;

        if(genericExec instanceof ValidationFailedException){
            exception = (ValidationFailedException) genericExec;

        }else if(genericExec instanceof AuthenticationFailedException){
            exception = (AuthenticationFailedException) genericExec;

        }else if(genericExec instanceof UnmarshalException){
            exception = (UnmarshalException) genericExec;
        }


        try {

            muleMessage.setPayload(exception);
            client.send("vm://" + getOutputQueue(), muleMessage);

        } catch (MuleException e) {
            // TODO Auto-generated catch block
            e.printStackTrace();
        }
    }

    public String getOutputQueue() {
        return outputQueue;
    }

    public void setOutputQueue(String outputQueue) {
        this.outputQueue = outputQueue;
    }

    public MuleContext getContext() {
        return context;
    }

    public void setContext(MuleContext context) {
        this.context = context;
    }
}

Answer 2

Mule抑制异常策略之外的异常。

对于您希望处理异常并将其作为回复发送的情况，将提供自定义转换器以准备具有异常的soap错误，然后在异常策略流程中将其设置为有效负载。

<flow name="ErrorHandling" doc:name="ErrorHandling" >
    <logger level="INFO" doc:name="Logger"/>
    <custom-transformer class="com.example.service.ErrorTransformer"></custom-transformer>
</flow>

用于准备错误消息的变换器。

@Override
public Object transformMessage(MuleMessage message, String outputEncoding)
        throws TransformerException {

    String exceptionMessage = message.getExceptionPayload().getException().getCause().getMessage() ;        

    String outputMessage = "<soap:Fault xmlns:soap=\"http://schemas.xmlsoap.org/soap/envelope/\">        " +
            " <faultcode>soap:Server</faultcode> " +
            "<faultstring>" + exceptionMessage + "</faultstring>      " +
            "</soap:Fault>";

    return outputMessage;
}

注意：这是一个示例变换器。根据您的情况自定义它。

如何在Mule中处理SOAP Web服务中的异常策略

2 个答案: