WSDL location and Port address location

[Sathees Tharmarajah]

Hi,

I have a question on access the WSDL and consuming the Service.

1) Can the wsdl location (server) http://localhost:8082/TestWebService/mathOperation?wsdl and in the WSDL file retrieved, following port address location BE DIFFERENT ?

<wsdl:service name="Test_Server">
<wsdl:port name="TestHttpSoap11Endpoint" binding="ns1:TestSoap11Binding">
<soap:address location="http://service:18082/services/Test_Server.Test_ServerHttpSoap11Endpoint"/>
</wsdl:port>

2) if above both addresses can be different how to implement that ?


thanks in advance

sathees

[Ivan Krizsan]

Hi!
I guess you want to know if the WSDL location of a web service can be significantly different from the web service endpoint address found in the WSDL.
If this is your question, then my answer is yes.
WSDLs may be stored in some kind of repository, perhaps even UDDI as envisioned in the past.
The WSDL is retrieved from the repository but the server on which the web service is deployed may be another computer.

The reason for storing the WSDLs in a repository of some sort may be that you want to be able to change the addresses of the web service endpoints.
By just modifying the address of the endpoint in the WSDL, you can redirect clients to different computers without having to modify the clients in any way.
Best wishes!

[Sathees Tharmarajah]

thank you for you value able reply, its gives me a clear idea about it.

[Arun Kumar]

I assume client stubs do not have to be regenerated just for address/location change. correct me If I am wrong.

[Ivan Krizsan]

Hi!
You are right, client artifacts do not need to be generated if only the address of the endpoint has changed.
The code snippet below shows how to modify the endpoint address:

...
...
// thePort is the port object of the service to invoke.
((BindingProvider)thePort).getRequestContext().put(Dispatch.ENDPOINT_ADDRESS_PROPERTY, "http://localhost:1234/JAX-WS_Server_wsgen/CalculatorService");
...

Best wishes!