Do you use the attribute 'location' 'location' in relation to the WSDL port?

My question relates to using the "location" attribute of an address element in a WSDL port binding.

Example WSDL snippet:

<wsdl:service name="serviceName">
    <wsdl:port binding="tns:serviceNameBIND" name="serviceNameBIND">
        <soap:address location="http://example.com" />
    </wsdl:port>
</wsdl:service>

I understand that the address element defines the URI of the host with which clients connect using the interface described by WSDL.

Hard coding the host URI into the generated client code seems curious. In a load balancing scenario, one URI makes sense. In my current environment, our customers are SOA components that support an external interface. Customers can access one of the four installations of our application. Load balancing goes even further.

There were other questions regarding SO regarding the location attribute, but they were mostly technology specific.

, , WSDL?

+5
1

location - . URL- .config, , , .config .

+3

All Articles