if you use JbossWS during the deployment
Jboss changed yourWS-URL into the adress
that is configurated under:
under the Tags
<mbean code="org.jboss.webservice.AxisService" name="jboss.ws4ee:service=AxisService"> <depends>jboss:service=WebService</depends> <attribute name="WebServiceHost">myPCName</attribute> <attribute name="WebServiceSecurePort">8443</attribute> <attribute name="WebServicePort">8080</attribute> <attribute name="ValidateWsdlRequest">false</attribute> </mbean>
there you can define your service Host Name.
all right now.
TOP! It works perfectly!
The wsdl for the server side deployment may contain a dummy service location, that JBossWS will adjust during deployment.
The wsdl for the client side deployment must contain the correct service location. i.e. the client must be told where to connect to.
You can override the location where the client obtains the wsdl from, like this
<service-ref> <service-ref-name>service/HelloService</service-ref-name> <wsdl-override>http://yourhost:8080/ws4ee-admindevel/HelloService?wsdl</wsdl-override> </service-ref>
Also the javax.xml.rpc.Stub interface contains a property with wich you can set the target endpoint address
Is there any better solution to this problem for large scale deployments? If we need to go down into the sar deployment and change this file for every box we deploy to, that significantly complicates our deployment of JBoss. Is there any way to have the WebServiceHost attribute reflect the actual hostname of the server the VM is running on?
This has been fixed in jboss-4.0.1