Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
Let's assume you have a wsdl with multiple ports running on localhost:8080. Today if you migrate this service to another machine myserver:8888, the only way to specify the new machine (without changing the wsdl) is to use the 'address' property once per port, repeating the url paths from the wsdl file.
For instance:
alias.arithmetics-ns=http://ode/bpel/test/arithmetics
arithmetics-ns.ArithmeticsService.GET_httpport.ode.address=http://myserver:8888/HttpBindingTest/ArithmeticsService/GET
arithmetics-ns.ArithmeticsService.POST_httpport.ode.address=http://myserver:8888/HttpBindingTest/ArithmeticsService/POST
Having two new properties 'host' and 'port' would allow to specify the new machine only once for all ports, without repeating the url paths.
The previous example would become:
alias.arithmetics-ns=http://ode/bpel/test/arithmetics
arithmetics-ns.ArithmeticsService.ode.host=myserver
arithmetics-ns.ArithmeticsService.ode.port=8888
One edge case is when (host or port) and address are set. The address property must take precedence over host or port properties.
So for instance, with the following endpoint file:
alias.arithmetics-ns=http://ode/bpel/test/arithmetics
arithmetics-ns.ArithmeticsService.ode.host=myserver
arithmetics-ns.ArithmeticsService.ode.port=8888
arithmetics-ns.ArithmeticsService.GET_httpport.ode.address=http://localhost:9090/HttpBindingTest/ArithmeticsService/GET
All service port addresses will point to the mahcine myserver:8888 except GET_httpport that would be invoked with the above url.