BTW, regardless of whether or not the services page is showing the wrong
endpoint URL, when you try to access the correct (expected) endpoint URL
to get the WSDL (?wsdl), not the one the services page is telling you to
use, can you see the WSDL from there? If yes, is the soapaddress field
(in wsdl:service/wsdl:port) correct?
The fact that the services page is incorrect is a bug that can be duly
recorded with a JIRA but many ask on this list how to turn off the
services page ("hide-service-list-page" option) to prevent people from
seeing the full list of WSDLs available (say, if a particular user is
only allowed to access a subset of the endpoints). The services page is
a nice-to-have feature but not a JAX-WS requirement and shouldn't be a
show-stopper for your work.
Your fastest solution is to go ahead and debug the server:
http://www.jroller.com/gmazza/entry/eclipse_debug_web_services and
supply us a patch. Somewhere our parsing algorithm is on the fritz,
that or the information it is getting from the "Apache load balancer"
(I'm not sure which product you're referring to, Googling is suggesting
both Tomcat and Apache server have them) is not supplying CXF the full
path information. If you haven't the time, to just submit a JIRA with
the simplest setup necessary to replicate the problem.
Glen
On 03/16/2012 09:27 AM, nkunkov wrote:
Glen,
We renamed the server. Still the same problem.
The URL gets cut off after first 7 characters:
Endpoint address: http://istesta/GetSearchResult
Again it's istesta instead of istestapp/myapp...
Is there anything else we can do? This will completely stall our
implementation on multiple client environments....
By the way when we configure IIS to redirect to the same URL - everything is
fine.
But when it's apache load balancer - the endpoing is invalid.
Thanks so much for your help.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Webservice-via-Load-Balancer-and-IIS-redirector-invalid-end-point-tp5566353p5571233.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Glen Mazza
Talend Community Coders - coders.talend.com
blog: www.jroller.com/gmazza
