schemaLocations in WSDL are wrong when JBoss EAP connector has proxy-name attribute

Issue

• I'm deploying a web service with an external schema referenced in the WSDL. When retrieving the WSDL, the schemaLocation attribute of the import has an incorrect host name when my JBossWeb connector has a proxy-name attribute set and I have the wsdl-host set in the webservices subsystem. For example, if my connector's proxy-name is set to test and the webservices subsystem has the wsdl-host set to jbossws, then the schemaLocation will have a host name of test. I would expect the wsdl-host to take precedence over the proxy-name.

• We are in a situation where, whenever we try to call a service (WSDL), registered on the DNS, going through a load balancer, the URL we see on wsdl:import is different from the URL we access on the browser. I ran a few tests using a different load balancer and the same situation happens. I have removed any mentions to the URL which appears on the WSDL from the server's and load balancer's hosts file but we're still seeing a different URL. If we access the instance directly through JBoss EAP, we see the correct URL. The balancing is done through an Apache Httpd using mod_jk.