UDDI Publishisng错误 [英] UDDI Publishisng error

问题描述

我正在使用UDDU发布向导并尝试发布我们自己的wcf服务。托管到IIS。使用wsHttpsbinding运行非常精细

发布向导时。我选择了指定网址并提供了网址，现在我收到错误了"请求因HTTP状态415失败：无法处理消息，因为内容类型为'text / xml; charset = utf-8'不是预期的类型'application / soap + xml; charset = utf-8'.."
当我试图发布现有的现有" HTTP：//localhost/ESB.ItineraryServices/ProcessItinerary.asmx "

" ------------------- --------
通讯错误
---------------------------
无法使用与服务器 http：//localhost/ESB.ItineraryServices/ProcessItinerary.asmx 进行通信。服务器无法识别HTTP标头SOAPAction的值：。
---------------------------
确定
---------------------------

我是ESb和UDDI的新人/>感谢您的帮助，Ritu

---

Rit

解决方案

您需要使用basicHttp绑定而不是wsHttp。该错误是因为basicHttp是连接到ASP.NET 2.0 ASMX服务的唯一绑定，而不是wsHttp。

感谢，

I am using UDDU publish wizard and trying to publish our own wcf service. hosted into IIS. running very fine using wsHttpsbinding

While publishing wizard. I have opted specify URL and provided URL now I am getting error 
" The request failed with HTTP status 415: Cannot process the message because the content type 'text/xml; charset=utf-8' was not the expected type 'application/soap+xml; charset=utf-8'.."


When I am trying to publish existing existing "http://localhost/ESB.ItineraryServices/ProcessItinerary.asmx"

"---------------------------
Communication Error
---------------------------
Unable to communicate with server http://localhost/ESB.ItineraryServices/ProcessItinerary.asmx. Server did not recognize the value of HTTP Header SOAPAction: .
---------------------------
OK  
---------------------------


I am new in ESb and UDDI  
Thanks for help , Ritu

---

Rit

解决方案

You need to use the basicHttp binding rather than wsHttp. The error is because basicHttp is the only binding that connects to ASP.NET 2.0 ASMX services, not wsHttp.

Thanks,

这篇关于UDDI Publishisng错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！