Bill,
If you use the WSDD file when you change machines, you don't have to bother
with the WSDL. Just re-deploy the WSDD file (which doesn't contain
machine-specific information) on whatever machine you like and voila, you'll
get a WSDL that contains that machine's information.
The specs for web services state that the machine name and port number be
part of the description for a service. In other words, the presence of the
machine and port there is essential so that clients can locate the service.
If I want to use the WSDL alone (and specifically not the WSDD) then I write
an Ant filter to strip out the old host/port and paste the new one. Shown
below is such a filter.
<replaceregexp file="${wsdl.dir}/MyService.wsdl"
match="https://Host1:Port1"; replace="https://Host2:Port2"/>
Anand
On Thu, 27 Jan 2005, Bill Keese wrote:
: It's inconvenient having the host name / port number in the WSDL file,
: like below, because every time you setup your service on a new machine
: you have to manually modify the WSDL file with the new machine's name.
: Do other people have a trick for dealing w/this inconvenience? Are
: people dynamically generating their WSDL files, similar to the way JSP
: pages are dynamically generated?
:
: <wsdl:service name="MyService">
: <wsdl:port binding="impl:InicioSoapBinding" name="MyService">
: <wsdlsoap:address location="http://localhost:8080/axis/services/MyService"/>
: </wsdl:port>
: </wsdl:service>
:
: Thanks,
: Bill
