本文介绍了不确定这是不是我的错误~~ vs2010 添加服务引用失败的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter

以上来自 Taleo 的 API 指南.
我正在尝试创建 WCF 客户端
(例如:创建您的第一个 WCF 客户端"
http://channel9.msdn.com/显示/端点/端点-Screencasts-Creating-Your-First-WCF-Client/ )

the above is from Taleo's API guide.
I'm trying to create a WCF Client
(e.g.: " Creating Your First WCF Client"
http://channel9.msdn.com/shows/Endpoint/Endpoint-Screencasts-Creating-Your-First-WCF-Client/ )

tbe.taleo... 链接来自 Taleo 的 API 文档.

The tbe.taleo... link is from Taleo's API documentation.

可能我的理解有问题.我的假设是当
来自 Taleo 的链接被输入到 vs2010添加服务引用"
对话框并点击GO,然后vs2010应该检索
从 Taleo 链接返回的正确 WSDL/SOAP 信封.
不会发生;而是发生错误.
Fiddler2 (http://fiddler2.com) 显示状态码 500
HTTP/1.1 500 内部服务器错误".[详细信息如下]

Likely my understanding is flawed. My assumption is that when the
link from Taleo is entered into the vs2010 "Add Service Reference"
dialog and GO is clicked, then vs2010 should retrieve
a proper WSDL/SOAP envelope back from the Taleo link.
That does not happen; instead an error occurs.
Fiddler2 (http://fiddler2.com) displays the status code 500
"HTTP/1.1 500 Internal Server Error". [FULL DETAILS BELOW]

"WcfTestClient.exe" 给出了类似的错误:[WcfTestClient DETAILS BELOW]

"WcfTestClient.exe" gives a similar error: [WcfTestClient DETAILS BELOW]

问题:是我,还是 Taleo 链接有问题?

QUESTION: is it me, or is the Taleo link flawed?

谢谢,
格里

[详细信息添加服务参考"]
HTML 文档不包含 Web 服务发现信息.元数据包含无法解析的引用:https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter".响应消息的内容类型 text/xml;charset=utf-8 与绑定的内容类型(application/soap+xml; charset=utf-8)不匹配.如果使用自定义编码器,请确保正确实现 IsContentTypeSupported 方法.响应的前 544 个字节是:'SOAP-ENV:协议不支持的内容类型application/soap+xml;charset=utf-8",必须是:text/xml"./MANAGER/dispatcher/servlet/rpcrouter

[FULL DETAILS "Add Service Reference"]
The HTML document does not contain Web service discovery information.Metadata contains a reference that cannot be resolved: 'https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter'.The content type text/xml;charset=utf-8 of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 544 bytes of the response were: 'SOAP-ENV:ProtocolUnsupported content type "application/soap+xml; charset=utf-8", must be: "text/xml"./MANAGER/dispatcher/servlet/rpcrouter

'.远程服务器返回错误:(500) 内部服务器错误.如果在当前解决方案中定义了服务,请尝试构建解决方案并再次添加服务引用.

'.The remote server returned an error: (500) Internal Server Error.If the service is defined in the current solution, try building the solution and adding the service reference again.

[WcfTestClient 详细信息]
错误:无法从 https://tbe.taleo.net/MANAGER/dispatcher/servlet 获取元数据/rpcrouter 如果这是您有权访问的 Windows (R) Communication Foundation 服务,请检查您是否已在指定地址启用元数据发布.有关启用元数据发布的帮助,请参阅位于 http://go 的 MSDN 文档.microsoft.com/fwlink/?LinkId=65455.WS-Metadata 交换错误 URI:https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter 元数据包含无法解析的引用:'https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter'.响应消息的内容类型 text/xml;charset=utf-8 与绑定的内容类型(application/soap+xml; charset=utf-8)不匹配.如果使用自定义编码器,请确保正确实现 IsContentTypeSupported 方法.响应的前 544 个字节是:'SOAP-ENV:ProtocolUnsupported content type "application/soap+xml;charset=utf-8",必须是:text/xml"./MANAGER/dispatcher/servlet/rpcrouter'.远程服务器返回错误:(500) Internal Server Error.HTTP GET 错误 URI:https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter HTML 文档不包含 Web 服务发现信息.

[WcfTestClient DETAILS]
Error: Cannot obtain Metadata from https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter If this is a Windows (R) Communication Foundation service to which you have access, please check that you have enabled metadata publishing at the specified address. For help enabling metadata publishing, please refer to the MSDN documentation at http://go.microsoft.com/fwlink/?LinkId=65455.WS-Metadata Exchange Error URI: https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter Metadata contains a reference that cannot be resolved: 'https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter'. The content type text/xml;charset=utf-8 of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 544 bytes of the response were: 'SOAP-ENV:ProtocolUnsupported content type "application/soap+xml; charset=utf-8", must be: "text/xml"./MANAGER/dispatcher/servlet/rpcrouter'. The remote server returned an error: (500) Internal Server Error.HTTP GET Error URI: https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter The HTML document does not contain Web service discovery information.

推荐答案

遗憾的是,我只能责怪自己.我观看了出色的免费 Pluralsight 视频.
我试图从 Taleo 的文档、谷歌、msdn 等中整理出来.

Sadly, I can only blame myself. I watched the excellent free Pluralsight videos.
I tried to sort it out from Taleo's documentation, Google, msdn, et cetera.

我应该使用这个:
http://tbe.taleo.net/wsdl/DispatcherAPI.wsdl
从这里:
http://tbe.taleo.net/products/TBE_API_Guide.pdf 来自
http://www.taleo.com/solutions/taleo-business-edition-web-integration-api

I should have used this:
http://tbe.taleo.net/wsdl/DispatcherAPI.wsdl
from here:
http://tbe.taleo.net/products/TBE_API_Guide.pdf from
http://www.taleo.com/solutions/taleo-business-edition-web-integration-api

感谢所有考虑过这个问题的人.
g.

Thanks to all who gave some thought to this issue.
g.

这篇关于不确定这是不是我的错误~~ vs2010 添加服务引用失败的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-11 10:44