Client calls .asmx, Server exposes WCF endpoint -
We have a client that is configured to connect to the ASMX service. We do not want to ask our customers to update their configuration, but we want to upgrade our service to use WCF. Does anyone know that WCF supports this? If so, what does the configuration file look like?
Our SMX service looks like this:
& lt; Binding & gt; & Lt; Compulsive name = "etresource soap" off timetimeout = "00:01:00" opentimeout = "00:01:00" get timeout = "00:10:00" sendTimeout = "00:01:00" cookies = "fottal" bypassprocede Allow = "False" hostNameComparisonMode = "StrongWildcard" maxBufferSize = "65536" maxBufferPoolSize = "524288" maxReceivedMessageSize = "65536" Message encoding = "text" text encoding = "UTF-8" transfer mode = "buffer" WebProxy = "true" & gt; & Lt; ReaderQuotas maxDepth = "32" maxStringContentLength = "8192" MacArray Lang = "16384" Maxbitespere Read = "4096" Max-nameTableConnect = "16384" /> & Lt; Safety Mode = "None" & gt; & Lt; Transport Client Credential Type = "None" Proxy Credential Type = "None" realm = "" /> & Lt; Message client credentials type = "user name" algorithm site = "default" /> & Lt; / Safety & gt; & Lt; / Binding & gt; & Lt; / BasicHttpBinding & gt; & Lt; / Binding & gt; & Lt; Customers & gt; & Lt; Endpoint address = "http: //.../atransaction.asmx" binding = "basic HttpBinding" binding configuration = "etunction sups" contract = "etunction sups" name = "etunction sups" / & gt;
In response to your follow-up question:
Any way to use WCF without changing the service URL?
Yes, you can make your .svc url re-direct .asmx url. This requires configuration changes on the service side as well as changes to your .asmx file but your existing client can continue to connect unchanged in any way. See.
Comments
Post a Comment