Multiple endpoints for a single contract in a WAS hosted WCF service?

If you need to expose several endpoints (for example, one with basicHttpBinding, and the other with netTcpBinding) for one contract in a heterogeneous environment, on a WAS server, how to do this?

Everything I read about the configuration of WAS endpoints indicates that the endpoint addresses and base addresses of the host should be empty, since WAS should automatically resolve addresses through the path to the .svc file and the protocol.

However, it is not possible to define an HTTP endpoint and a TCP endpoint for the same contract without explanation of addresses. Each of my attempts so far has tied me to the coveted "binding error, which was already associated with listening to uri".

Ideas?

thank

+3
source share
2 answers

See if this works for you http://knowledgebaseworld.blogspot.com/2010/06/domain-name-replaced-with-machine-name.html I was hainvg the same problem that the "binding instance was already linked to listening uri ", which is fixed by adding httpGetUrl along with the binding address

+1
source

, *.svc HTTP, . basicHttpBinding. : - URI , , , SVC , SVC .

, HTTP- , SVC HTTP-.

, http, netTcpBinding. (, ) web.config.

0

Source: https://habr.com/ru/post/1751447/


All Articles