Hi Christian,
NO , you can't specify a full URL address instead of the related path
for the endpoint which you want to publish with the Servlet transport.
Because CXFServlet can't know your Web container's listen port and
related context, so it alway update the endpoint's address with the
request URL even you specify it with the jax-ws-configuration.
But if you publish the endpoint with the Jetty http standalone
transport. I think you can get what you want.
Willem.
Christian Vest Hansen wrote:
It's a bit late over here so I can't test this right now, but I
suppose that the endpointName and address attributes of the
jaxws:endpoint element as listed here:
http://cwiki.apache.org/CXF20DOC/jax-ws-configuration.html are exactly
what I want, provided that cxf honors those values and put them in the
WSDL?
If so, then there's no need to file a new jira.
2007/10/30, Willem2 <[EMAIL PROTECTED]>:
Now , CXFServlet always updates the endpoint's address with the request url.
You can fill a JIRA[1] with your wishes.
[1]http://issues.apache.org/jira/browse/CXF
Willem.
Christian Vest Hansen wrote:
I deploy a CXF web service to a cluster that sits behind a content switch.
We have HTTPS on the content switch for security, but internally in
the cluster we use plain HTTP for speed.
Now, CXF has a habit of rewriting my carefully crafted endpoint URLs
in my WSDL, thus reporting plain HTTP endpoints on the services/ page
and in the final WSDL, when in fact they should be HTTPS.
Is there a way configure this behavior?
--
Venlig hilsen / Kind regards,
Christian Vest Hansen.
--
View this message in context:
http://www.nabble.com/endpoint-rewriting-tf4717550.html#a13488677
Sent from the cxf-user mailing list archive at Nabble.com.
