创建服务器代理以调用工作流服务 [英] Creating a server proxy to call a Work Flow service

查看:70
本文介绍了创建服务器代理以调用工作流服务的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

当我调用新的worflow服务时,出现以下错误.我在创建代理时遇到了不同的问题,并解决了各种问题,但是这个问题仍然存在.似乎名称空间不正确,但是我一直在检查,并且在WF服务和请求类的服务合同属性中似乎都可以.关于寻找什么的任何想法表示赞赏.

************************************
由于EndpointDispatcher上的ContractFilter不匹配,因此无法在接收方处理带有操作"[Name]"的消息.这可能是由于合同不匹配(发送方和接收方之间的操作不匹配)或发送方和接收方之间的绑定/安全不匹配. **************************************


When I am calling a new worflow service, I am getting the following error. I have been having different problems with creating a proxy and have resolved various issues, but this one is still remaining. It appears the namespace is not correct, but I have been checking and it appears to be ok in both the WF service and the service contract attribute of the request class. Any ideas on what to look for is appreciated.

***********************************
The message with Action ''[Name]'' 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.contract mismatch.
**********************************


Discovered that my request class (i.e. data contract) is not being declarated correctly upon being serialized. The working request message looks something like this:
<SetDate xmlns='http://company.com/ns/2010/05/'>
<request xmlns:a='http://company.com/ns/2010/05/' xmlns:i='http://www.w3.org/2001/XMLSchema-instance'>
<a:ID i:nil='true'></a:ID>
<a:IndexId>0</a:IndexId>
<a:UserName i:nil='true'></a:UserName>
<a:CreatedBy i:nil='true'></a:CreatedBy>
</request>
</SetDate>
 The data contract that does not work is:
<SetDate xmlns='http://company.com/ns/2010/05/'>
<request xmlns:i='http://www.w3.org/2001/XMLSchema-instance'>
<ID i:nil='true'>
</ID>
<IndexId>0</IndexId>
<UserName i:nil='true'></UserName>
<CreatedBy i:nil='true'></CreatedBy>
</request>
</SetDate>
 Why would the serialization be so different? First request is serialized using a web reference - request class being used is apart of the web reference. The second, was found by executing the service from a proxy class (ie. creating a channel - etc) and instantiating a request class (data contract).

 Trying to figure out why my declarations are different. Any suggestions are greating appreciated.

推荐答案

对于此特定项目,我选择使用Web服务.这样就解决了问题.
For this particular project, I chose to use a web service. This resolved the problem.


这篇关于创建服务器代理以调用工作流服务的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆