Hi ZJH
I've been thinking about this - I don't know enough about your setup (your web.config or your .wsdl) to give you much advice.
Firstly - the trouble with you editing the web.config or a .wsdl is that there can be intradependencies (within the files) and interdependencies (between the files) depending on the content of your files that unless you are completely aware of them all - you can cause more problems and become unstuck - I've seen one instance where the person messed things up in the config to the point that he ended up rebuilding the whole webservice to reset everything.
Next - considering all the interdependencies that can occur in a .wsdl - if I were you - you need to compare the old .wsdl with the old web.config. Determine which attributes are equivalent to them, then update them properly - what I mean by this is that 'bindingConfiguration' in your web.config appears to equate to the 'binding' attribute in a .wsdl, etc.
Worst case - just to verify if you have the endpoint (server and URI) correct - rather than edit anything for now - why not create a new endpoint on your SOAP request in a test (in the SoapUI tab) and try both options?
e.g.
new endpoint --> https://amanda-as-dev72:8080/axis/services/WSAmandaService/
new endpoint --> https://amanda-as-dev72:8080/axis/services/WSAmandaService.WSAmandaServiceHttpsSoap11Endpoint/
At least you'll be able to see which endpoint is valid?
If the old web.config included '/axis/services/WSAmandaService.WSAmandaServiceHttpsSoap11Endpoint/' as the URI to your endpoint and the endpoint in your .wsdl is '/axis/services/WSAmandaService' then I'd consider maintaining this for now - but as I say - personally - I'd look at the existing web.config and the existing .wsdl and map each of the equivalent attributes so I'm positive I know what I'm changing is correct. ONLY at this point would I then look at the new .wsdl to consider changing the URI in the web.config.
Sorry - I can't give you the 'right' answer cos I don't know your setup - but the above is the approach I would use.
ta
rich