Re: inconvenient host name / port # in WSDL file

2005-01-27 Thread Anand Natrajan
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

Re: inconvenient host name / port # in WSDL file

2005-01-27 Thread Patrick Cogan
Using Axis RC2 it automatically substitutes the correct url of the machine it is running on, regardless of what the actual value is in the wsdl. This works even if you specify in the deploy.wsdd /xxx.wsdlunder element for you service. Regards, Patrick. On Thu, 27 Jan 2005 09:10:18 +0900, Bill

Re: inconvenient host name / port # in WSDL file

2005-01-26 Thread Peter Molettiere
On Jan 26, 2005, at 4:10 PM, 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. Look at the filtering="on" option on th

inconvenient host name / port # in WSDL file

2005-01-26 Thread Bill Keese
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