Spring-WS - 在异常时返回有效响应

luk*_*isp 2 spring spring-ws exception

我有soap和point,它应该根据请求类型B返回响应类型A。但是在处理请求期间,我期望出现错误(例如无法调用下游服务),这些错误会抛出异常异常,例如ExpEx类型。现在我要做自定义错误映射,因为如果出现错误,我不想返回类型 A,而是想返回类型 CFault(也在 wsd 中定义)。现在问题: - 是否可以创建自定义 eero 句柄,将 CFault 改为 A - 或者是否可以使 enpoint 允许返回两种类型的响应 A 和 CFault (我认为是对象)?

我的要点:

public class FantasticEndpoint extend WebServiceEndpoint {
private static final String NAMESPACE = "http://www.fantastic.com/SOA/tmp/FantasticService/v_2_4";

@PayloadRoot(namespace = NAMESPACE, localPart = "handleBOperation")
@ResponsePayload
public A createConsumers(@RequestPayload B b{
    //do some dangerous logic possility throw EXCEPTION
        // if EXCEPTION return CFault or return A if normal processing
}
Run Code Online (Sandbox Code Playgroud)

}

小智 6

首先,看一下:https://docs.spring.io/spring-ws/sites/2.0/reference/html/server.html#server-endpoint-exception-resolver

我将强调其中的一些内容:

根据文档,您可以创建自己的异常类来指示每当引发该异常时应返回的 SOAP 错误。只需使用 @SoapFault 注释来注释类即可。

import org.springframework.ws.soap.server.endpoint.annotation.FaultCode;
import org.springframework.ws.soap.server.endpoint.annotation.SoapFault;

@SoapFault(faultCode = FaultCode.SERVER)
public class MyCustomException extends Exception {
    public MyClientException(String message) {
        super(message);
    }
}
Run Code Online (Sandbox Code Playgroud)

如果这不适合您,您可以使用 SoapFaultAnnotationExceptionResolver ( https://docs.spring.io/spring-ws/site/apidocs/org/springframework/ws/soap/server/endpoint/SoapFaultAnnotationExceptionResolver.html )。该解析器允许您将异常类映射到 SOAP 错误:

<beans>
    <bean id="exceptionResolver" class="org.springframework.ws.soap.server.endpoint.SoapFaultMappingExceptionResolver">
    <property name="defaultFault" value="SERVER"/>
    <property name="exceptionMappings">
        <value>
            org.springframework.oxm.ValidationFailureException=CLIENT,Invalid request
        </value>
    </property>
</bean>
Run Code Online (Sandbox Code Playgroud)

您可以使用它来添加 SoapFaultDetail:

public class MySoapFaultDefinitionExceptionResolver extends SoapFaultMappingExceptionResolver {

private static final QName CODE = new QName("code");
private static final QName DESCRIPTION = new QName("description");

@Override
protected void customizeFault(Object endpoint, Exception ex, SoapFault fault) {
    if (ex instanceof MyCustomException) {
        SoapFaultDetail detail = fault.addFaultDetail();
        detail.addFaultDetailElement(CODE).addText("SOMECODE");
        detail.addFaultDetailElement(DESCRIPTION).addText(ex.getMessage());
    }
}
Run Code Online (Sandbox Code Playgroud)

我曾经使用 EndpointInterceptor 来搞乱 SOAPHeader。也许您可以使用它来完成 SOAPFault 的工作(https://docs.spring.io/spring-ws/site/apidocs/org/springframework/ws/server/EndpointInterceptor.html)。

您可以像这样从 MessageContext 中提取 SOAPFault:

@Override
public boolean handleFault(MessageContext messageContext, Object o) throws Exception {
    SaajSoapMessage soapResponse = (SaajSoapMessage) messageContext.getResponse();
    SOAPMessage soapMessage = soapResponse.getSaajMessage();
    SOAPBody body = soapMessage.getSOAPBody();
    SOAPFault fault = body.getFault();
    //do something with fault here
    return true
}
Run Code Online (Sandbox Code Playgroud)

您可以在此处阅读有关 SOAPFault 接口的信息https://docs.spring.io/spring-ws/site/apidocs/org/springframework/ws/soap/SoapFault.html