Design/Deployment Question Relating to WSDL location attribute
I have a general question/problem regarding WSDL design and syntax that we have been wondering about at our company.
In WSDL, from everything we've seen and learned, the "address location" is hard-coded:
That being so, how do you deploy (somewhat elegantly) the same war (i.e. same source code, i.e. same app funtionality version) to multiple servers without having to manually modify the wsdl for each one of them? Is there a way to "soft-code" the location attribute in the wsld, so that it can be picked up at deploy-time from some kind of properties file?
<wsdl:port binding="tns:MySOAPBinding" name="MySOAPBindingPort">
We had also thought about writing a program to soft-populate the value by writing a simple program to modify the location, and then making that program be part of the deployment script after the war has been unpacked by tomcat.
We're thinking that most everyone in the WSDL world must have this problem, or perhaps we're missing something simple?