Jax-ws异常序列化失败

3
我遇到了一个问题,无法找到解决方法(或者我正在错误的解决方法)。当我的服务生成某些异常时,似乎序列化会失败。这导致获得一个包装的异常,这很痛苦,因为调用客户端接收到的错误信息很差,我想我从原始异常中丢失了有用的信息。
在下面的示例中,是S3存储桶访问问题,但我也遇到了一些SQL异常类似的问题。
如果我能够使我的服务直接介入,那将非常有用。理想情况下,应添加一些自定义异常序列化代码。
> com.amazonaws.services.simpleworkflow.flow.DataConverterException:
> Failure serializing
> "com.sun.xml.internal.ws.fault.ServerSOAPFaultException: Client
> received SOAP Fault from server: Access Denied (Service: Amazon S3;
> Status Code: 403; Error Code: AccessDenied; Request ID: AAAAAAAAAAAA)
> Please see the server log to find more detail regarding exact cause of
> the failure." of type "class
> com.sun.xml.internal.ws.fault.ServerSOAPFaultException" when mapping
> key "null" at
> com.amazonaws.services.simpleworkflow.flow.JsonDataConverter.throwDataConverterException(JsonDataConverter.java:90)
> at
> com.amazonaws.services.simpleworkflow.flow.JsonDataConverter.toData(JsonDataConverter.java:78)
> at
> com.amazonaws.services.simpleworkflow.flow.pojo.POJOActivityImplementation.throwActivityFailureException(POJOActivityImplementation.java:102)
> at
> com.amazonaws.services.simpleworkflow.flow.pojo.POJOActivityImplementation.execute(POJOActivityImplementation.java:67)
> at
> com.amazonaws.services.simpleworkflow.flow.generic.ActivityImplementationBase.execute(ActivityImplementationBase.java:46)
> at
> com.amazonaws.services.simpleworkflow.flow.worker.SynchronousActivityTaskPoller.execute(SynchronousActivityTaskPoller.java:196)
> at
> com.amazonaws.services.simpleworkflow.flow.worker.ActivityTaskPoller$2.run(ActivityTaskPoller.java:92)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748) Caused by:
> com.fasterxml.jackson.databind.JsonMappingException: Type id handling
> not implemented for type org.w3c.dom.Node (by serializer of type
> com.fasterxml.jackson.databind.ext.DOMSerializer) (through reference
> chain:
> com.sun.xml.internal.ws.fault.ServerSOAPFaultException["fault"]) at
> com.fasterxml.jackson.databind.SerializerProvider.mappingException(SerializerProvider.java:1084)
> at
> com.fasterxml.jackson.databind.JsonSerializer.serializeWithType(JsonSerializer.java:159)
> at
> com.fasterxml.jackson.databind.ser.BeanPropertyWriter.serializeAsField(BeanPropertyWriter.java:695)
> at
> com.fasterxml.jackson.databind.ser.std.BeanSerializerBase.serializeFields(BeanSerializerBase.java:675)
> at
> com.fasterxml.jackson.databind.ser.std.BeanSerializerBase.serializeWithType(BeanSerializerBase.java:566)
> at
> com.fasterxml.jackson.databind.ser.impl.TypeWrappedSerializer.serialize(TypeWrappedSerializer.java:32)
> at
> com.fasterxml.jackson.databind.ser.DefaultSerializerProvider.serializeValue(DefaultSerializerProvider.java:130)
> at
> com.fasterxml.jackson.databind.ObjectMapper._configAndWriteValue(ObjectMapper.java:3559)
> at
> com.fasterxml.jackson.databind.ObjectMapper.writeValueAsString(ObjectMapper.java:2927)
> at
> com.amazonaws.services.simpleworkflow.flow.JsonDataConverter.toData(JsonDataConverter.java:72)
> ... 8 more

感谢任何建议


SOAP服务返回403?使用JSON格式?你的问题中有些内容不够清晰。你是在将SOAP映射到JSON吗? - Namphibian
1个回答

1

Jackson正在尝试序列化com.sun.xml.internal.ws.fault.ServerSOAPFaultException的某个实例。这个异常是javax.xml.ws.soap.SOAPFaultException的一个子类,它恰好有一个用于检索SOAPFault的getter。由于SOAPFault是一个DOM Node,Jackson决定使用DOMSerializer并编码类型信息,以便在反序列化时可以找到fault是哪种具体类型的实例。问题是DOMSerializer不支持这种类型信息,所以你会得到com.fasterxml.jackson.databind.JsonMappingException
我认为解决这个问题的最佳方法是注册一个自定义的SOAPFault序列化器/反序列化器对。然后,您可以将其序列化为String并通过其中一个{{link1:SOAPFactory.createFault(...)方法}}创建新实例进行反序列化。不要忘记还要实现JsonSerializer.serializeWithType(...),以便Jackson可以正确处理类型。
public class SOAPFaultSerializer extends StdSerializer<SOAPFault> {

    public SOAPFaultSerializer() {
        this(null);
    }

    public SOAPFaultSerializer(Class<SOAPFault> t) {
        super(t);
    }

    @Override
    public void serialize(SOAPFault fault, JsonGenerator jgen, SerializerProvider provider) throws IOException, JsonProcessingException {

        jgen.writeStartObject();
        // serialize "interesting" SOAPFault information
        jgen.writeStringField("faultActor", fault.getFaultActor());
        jgen.writeStringField("faultCode", fault.getFaultCode());
        ...
        jgen.writeEndObject();
    }

    @Override
    public void serializeWithType(JsonGenerator jgen, SerializerProvider provider, TypeSerializer typeSer) throws IOException, JsonGenerationException {
        typeSer.writeTypePrefixForObject(this, jgen, SOAPFault.class);
        serialize(value, jgen, provider);
        typeSer.writeTypeSuffixForObject(this, jgen);
    }
}

public class SOAPFaultDeserializer extends StdDeserializer<SOAPFault> { 

    public SOAPFaultDeserializer() { 
        this(null); 
    } 

    public SOAPFaultDeserializer(Class<?> vc) { 
         super(vc); 
    }

    @Override
    public SOAPFault deserialize(JsonParser jp, DeserializationContext ctxt) throws IOException, JsonProcessingException {
         JsonNode node = jp.getCodec().readTree(jp);
         // deserialize "interesting" SOAPFault information
         String faultActor = node.get("faultActor").asText();
         String faultCode = node.get("faultCode").asText();
         ...
         SOAPFactory factory = SOAPFactory.newInstance();
         SOAPFault fault = factory.createFault();
         // fill in SOAPFault with deserialized fields
         fault.setFaultActor(faultActor);
         fault.setFaultCode(faultCode);
         ...
         return fault;
    }
}

请记住,SOAPFactory.newInstance() 可能会相对昂贵,因此如果您需要高性能,应尝试仅调用此方法一次并重复使用工厂实例。 - gpeche
好的,谢谢。 - Jon Whitefield

网页内容由stack overflow 提供, 点击上面的
可以查看英文原文,
原文链接