I recently discovered that the ports used for the WSDL and service listing 
produced by CXF seems effected when running behind an Apache load balancer.  
I'm running WebLogic in clustered mode and specifying a frontend-http-port of 
80.  Each backend server is bound to a different port.  When I develop and 
deploy locally, without the cluster portion of WL enabled and without a load 
balancer, the CXF service list web page displays the port normally (7001).  But 
when I run the same war on a clustered server the port changes to the load 
balanced port (80).  For example the endpoint changes from 
http://foo:7001/simpleservice/myservice to 
http://foo:80/simpleservice/myservice.  Likewise the WSDL reflects the 
different ports.

Could someone point me to the CXF code that controls what ports are displayed 
in the WSDL urls and service listing?  I'm very curious how CXF knew to use the 
load balanced port.  It seems to be the correct behavior but I'd like to 
understand it better.

Thanks,

Brandon Richins

Reply via email to