generated wsdl always has port 8080 (even when it should be

[gsmithfarmer]

Tomcat listening on 8180 (using straight ports-01).
wsdl viewed via a browser (e.g. http://localhost:8180/...?wsdl) wsdl says port 8080:


-
<soap:address location="http://s01-bwfpl022:8080/HelloWorld/HelloWorldBean" />



Naturally, my client fails to attach. (If I have the client use a local wsdl that has the correct port all works fine).

JBoss: 4.0.5.GA
JRE: 1.5.0_10-b03
O/S: XP or RHEL -- does not seem to make a difference.

Other than creating a servers-binding.xml file (from the samples dir) and changing jboss-services to use "ports-01", my jboss is a plain vanilla install using jems-installer-1.2.0.GA.jar (ejb3 set).

[gsmithfarmer]

Simplified question:

ServiceEndpoint in the generated wsdl is always 8080. (Even when tomcat is listening on 8180).
Why? What configuration am i missing.

[dlofthouse]

http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQURLRewriting

[romeufigueira]

Simplified answer:

File: modify /server/default/deploy/jbossweb-tomcat55.sar/server.xml
Change: <Connector port="8180" address="${jboss.bind.address}"
Motive: Makes JBoss AS run on port 8180 instead of the previous 8080

File: modify /server/default/deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml
expload and remove jbossws.beans
Change: <property name="webServicePort">8180</property>
Motive: Makes JBoss WS check properly port 8180

[gsmithfarmer]

Thanks for the replies. The actual solution was simpler -- I finally saw it because your replies referenced config files not in my jboss instance.

The underlying problem:

jems-installer-1.2.0.GA.jar contains jbossws 1.0.3.SP1. I assumed that is contained a GA version of jbossws.


Simply replace with a current jbossws (like 1.0.4.GA) and the endpoint rewrite problem is solved.