Soap org.mule.api.transport.DispatchException-消息负载的类型为:PostMethod

Soap org.mule.api.transport.DispatchException-消息负载的类型为:PostMethod,soap,https,mule,esb,Soap,Https,Mule,Esb,我在通过https connnector发送请求时遇到问题。当我在SoapUi中准备mock时,并没有任何问题,但现在我正在尝试与其他系统集成。看起来标题可能有问题,但我不知道到底是什么。。。我在这个示例中创建了地址 <message-properties-transformer> <add-message-property key="SOAPAction" value="http://address"/> </message-pro

我在通过https connnector发送请求时遇到问题。当我在SoapUi中准备mock时,并没有任何问题,但现在我正在尝试与其他系统集成。看起来标题可能有问题,但我不知道到底是什么。。。我在这个示例中创建了地址

    <message-properties-transformer>
        <add-message-property key="SOAPAction" value="http://address"/>
    </message-properties-transformer>
    <logger level="INFO" message="#[payload]" />

    <https:outbound-endpoint  exchange-pattern="request-response" address="${adapter.ws.endpoint}"
        responseTransformer-refs="dom2xml-transformer" connector-ref="httpsConnector">
        <cxf:proxy-client payload="body"
            enableMuleSoapHeaders="false">
            <cxf:inInterceptors>
                <spring:ref bean="cxfLoggingInInterceptor" />
            </cxf:inInterceptors>
            <cxf:inFaultInterceptors>
                <spring:ref bean="cxfLoggingInInterceptor" />
            </cxf:inFaultInterceptors>
            <cxf:outInterceptors>
                <spring:ref bean="WssOutInterceptor" />
                <spring:ref bean="cxfLoggingOutInterceptor" />
            </cxf:outInterceptors>
            <cxf:outFaultInterceptors>
                <spring:ref bean="cxfLoggingOutInterceptor" />
            </cxf:outFaultInterceptors>
        </cxf:proxy-client>
    </https:outbound-endpoint>

问题出在X-MULE_会议上。如果其中两个服务正在使用mule esb,则应该在同一个mule会话中实现。有一个解决方法:

<https:connector name="httpsNoSessionConnector">
     <service-overrides sessionHandler="org.mule.session.NullSessionHandler" />
</https:connector>

答案张贴在那里:

我认为这不是因为响应标题。它来自于反应本身。响应对象可用吗?如果是这样,请在OP中发布。不幸的是,这是因为X-MULE_会话头
X-MULE_ENCODING UTF-8
#status# HTTP/1.1 200 OK
http.method POST // ?? should it be there?
X-MULE_CORRELATION_SEQUENCE -1
Connection Keep-Alive
Server Mule Core/3.5.0
Date Tue, 23 Dec 2014 12:04:49 GMT
Transfer-Encoding chunked
Via 1.1 pl.service.pl
Keep-Alive timeout=15, max=100
Content-Type text/xml; charset=UTF-8
X-MULE_SESSION rO0ABXNyACNvcmcubXVsZS5zZXNzaW9uLkRlZmF1bHRNdWxlU2Vzc2lvbi7rdtEW7GGKAwAFWgAFdmFsaWRMAA1mbG93Q29uc3RydWN0dAAmTG9yZy9tdWxlL2FwaS9jb25zdHJ1Y3QvRmxvd0NvbnN0c
<https:connector name="httpsNoSessionConnector">
     <service-overrides sessionHandler="org.mule.session.NullSessionHandler" />
</https:connector>