Setup info 1:
The setup has in deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml the following lines commented:

<property name="webServiceHost">${jboss.bind.address}</property>
<property name="webServicePort">8080</property>

This should result in the protocol, port and the host being picked up from requesters URL.

Setup info 2:
I have JBoss server setup behind apache server. Apache web server forwards request to the JBoss Server using mod_jk. The host ip for the apache server is 38.187.114.136. The host ip for the JBoss server is 38.187.114.238. The JBoss web services are bound to port 8180.

Observer behavior:
When I access the WSDL using http:/38.187.114.136/application/SessionService?wsdl the WSDL I received has the following information:
<definitions name="InitMethod" targetNamespace="http://com.foo.service/callcontrol">
<types>
<xsd:schema>
<xsd:import namespace="http://com.foo.service/callcontrol/types" schemaLocation="http://38.187.114.136/service/SessionService?wsdl&resource=Session.xsd"/>
</xsd:schema>

.....
.....
.....

<port binding="ns2:SessionServiceBinding" name="SessionServicePort">
<soap:address location="http://38.187.114.136:8180/service/SessionService"/>
</port>
</service>
</definitions>

Problem description:

• schemaLocation is right. It is using requesters protocol, port and host "http://38.187.114.136/service/SessionService?wsdl&resource=Session.xsd"
• soap:address location does not match schemaLocation. It does not use the port corresponding to the request and instead provides port where the service is running - "http://38.187.114.136:8180/service/SessionService"