Some strange with the WSDL generated during asadmin deploy

Hi devs and users,

I'have created WebService with @WebServices annotation,

packaged and deploy it with asadmin.

When accessing the WSDL via

http://192.168.1.1:8080/test/TestService?WSDL

the WSDL contain something like this:

[...]

<types>

<xsd:schema>

<xsd:import namespace="http://xyz/"

schemaLocation="http://testserver:8080/test/TestService/__container$publishing$ subctx/WEB-INF/wsdl/TestService_schema1.xsd"

xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"

xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"/>

</xsd:schema>

</types>

[...]

<service name="NotificationSystemService">

<port name="NotificationSystemPort" binding="tns:NotificationSystemPortBinding">

<soap:address

location="http://testserver:8080/test/TestService"

xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"

xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"/>

</port>

</service>

[...]

Note that, the soap:address and schemaLocation use the hostname 'testserver', but not the ip address '192.168.1.1'.

How can I control the AS so that, when it generate the WSDL, it use the host address, instead of the hostname.

[1292 byte] By [zarick@gmail.coma] at [2007-11-15]