2012-01-26 54 views
4

我遇到了Savon Ruby Gem生成SOAP API调用失败的问题,但是当我复制并粘贴确切的相同的XML消息进入SOAP-UI成功。使用Savon SOAP客户端API调用结果EndFileDispatcher中的ContractFilter不匹配错误

我发送这样的信息:

<?xml version="1.0" encoding="UTF-8"?> 
<soapenv:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tem="http://tempuri.org/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:vis="http://schemas.datacontract.org/2004/07/Vision.SecureOriginCommand.ServiceContracts"> 
<soapenv:Body> 
    <tem:CameraConfiguration> 
    <tem:request> 
    <vis:ClientToken>5555</vis:ClientToken> 
    <vis:DeviceID>26219</vis:DeviceID> 
    <vis:Enabled>1</vis:Enabled> 
    <vis:Interval>60</vis:Interval> 
    </tem:request> 
</tem:CameraConfiguration> 
</soapenv:Body> 

向该API(A远程网络摄像机配置): https://oapqa.onasset.com/Services/SecureOriginCommand.svc?wsdl

但失败,此消息:

SOAP response (status 500): 
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"> 
<s:Body> 
<s:Fault><faultcode xmlns:a="http://schemas.microsoft.com/ws/2005/05/addressing/none">a:ActionNotSupported</faultcode> 
<faultstring xml:lang="en-US">The message with Action 'oapSetSentryReportingIntervalRequest' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None)</faultstring> 
</s:Fault> 
</s:Body> 

我的第一个想法是,我必须在行动名称中输入一个错字。但是 没有,当我在SOAP-UI尝试完全一样的消息,我得到以下 成功:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"> 
    <s:Body> 
    <CameraConfigurationResponse xmlns="http://tempuri.org/"> 
    <CameraConfigurationResult xmlns:a="http://schemas.datacontract.org/2004/07/Vision.SecureOriginCommand.ServiceContracts" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"> 
     <a:Error/> 
     <a:Result>true</a:Result> 
    </CameraConfigurationResult> 
    </CameraConfigurationResponse> 
</s:Body> 
</s:Envelope> 

这使我相信,这个问题是不是由格式引起我的XML消息的 但用我配置我的客户端的方式。下面是实际的代码:

Savon.configure do |config| 
config.log = :debug 
config.env_namespace = :soapenv 
config.raise_errors = false 
end 

# TODO Enable ssl certficate verification 
client = Savon::Client.new do 
    wsdl.document = TARGET_SO_WSDL 
    http.auth.ssl.verify_mode = :none 
end 

resp = client.request 'tem', 'CameraConfiguration' do 
    soap.namespaces['xmlns:vis'] = 'http://schemas.datacontract.org/2004/07/Vision.SecureOriginCommand.ServiceContracts' 
    soap.namespaces['xmlns:tem'] = 'http://tempuri.org/' 
    soap.body = { 
    'tem:request' => { 
     'vis:ClientToken' => ON_ASSET_API_KEY, 
     'vis:DeviceID' => webcam.gps_device.device_id, 
     'vis:Enabled' => 1, 
     'vis:Interval' => webcam.report_interval 
    } 
    } 
end 

跟我谈过的谁维护我试图 访问API的开发人员。我想他的反应可以提供一个线索:

Binding on the RemoteSentryService was set to mexHttpBinding instead of mexHttpsBinding. 


I don’t think this should give you a fault exception, because its working on .NET simulator client I have. And this endpoint is only used to generate the wsdl (MetaExchange Binding). But, given you are using a different client, I would still give it a shot. 

I also regenerated the proxy from wsdl and updated my sample simulator and it looks good. 

这是问题的一个已知的问题与萨翁和Microsoft SOAP 端点或HTTPS?或者这个问题只是我遇到的问题?

回答

5

调试它并注意到萨翁不幸发送了正确的SOAPAction HTTP头。仅供参考:通过soapUI发送SOAP请求后,您可以点击“RAW”选项卡(在请求窗口垂直对齐)进一步调查。

下面是完整的例子:

client = Savon::Client.new do 
    wsdl.document = TARGET_SO_WSDL 
    http.auth.ssl.verify_mode = :none 
end 

resp = client.request 'tem', 'CameraConfiguration' do 
    # Notice, that the SOAPAction needs to the wrapped in double quotes: 
    http.headers['SOAPAction'] = %("http://tempuri.org/ISecureOriginCommand/CameraConfiguration") 
    soap.namespaces['xmlns:vis'] = 'http://schemas.datacontract.org/2004/07/Vision.SecureOriginCommand.ServiceContracts' 
    soap.body = { 
    'tem:request' => { 
     'vis:ClientToken' => 5555, 
     'vis:DeviceID' => 26219, 
     'vis:Enabled' => 1, 
     'vis:Interval' => 60 
    } 
    } 
end 

希望工程为您服务!

+1

这看起来像是有效的。谢谢。我真的很感激你花时间去调试,这真是太好了。并感谢肥皂用户提示。 – Frank

+0

不客气:) – rubiii

+1

哇,这是我确切的问题。感谢一百万张贴。那么这是Savon中的一个错误还是某种互操作性问题? –

相关问题