Hi,
OK this use case probably doesn't occur very often and it can be worked around, but I thought I'd post this anyway to see if a) anyone else has run into it, and b) if the Business Consultant is correct that this is actually configurable, or if as I suspect, it's not.
I've been working with a client on a proof-of-concept that requires the web services. We're doing this in CS 16.0. The POC servers are all hosted on MS Azure and we're behind a corporate firewall. If you try and do the WSImport against the FQDN, it hits a bunch of errors. When I examined the WSDL file itself, I discovered why. Within the WSDL, if additional calls out are required, they are done with the hostname in the URL and not the FQDN. If you're importing from a client that is not local to the server you're calling for the WSDL, it will fail on these subsequent calls. My suspicion is that the generation of the WSDL automatically uses the host name and not the FQDN within the WSDL for the various xsd elements, and I suspect that this is not something that is easily configurable. If it is, I'd love to know. And once again, I know, who would otherwise try and do a WSImport against a remote server across the internet?
-Hugh
