Web Service Endpoint Substitution

You can experiment with different Web service implementations, such as those supplied by third parties, by substituting one Web service endpoint for another as long as they are compatible with each other, for example, they have the same operations interface and can handle the same messages. By convention, the combination of a Web service's WSDL binding name and binding namespace identifies the behavior of the Web service. When you connect Web service endpoints, the WSDL Binding Name and WSDL Binding Namespace properties on the endpoints determine whether the endpoints are compatible.


A warning appears when connecting endpoints that do not have matching WSDL binding names or namespaces; however, such endpoints can still be connected. Even if the binding name and namespaces match between endpoints, there is no guarantee that the endpoints have compatible behavior, message schemas, or that their associated applications have correctly implemented their specification. It is recommended that you test the behavior of connected applications or risk discovering these incompatibilities at run time. For more information, see How to: Substitute Web Services on Application Diagrams.

See Also


Overview of Endpoints on Applications

Web Service Endpoints Based on WSDL Files