With 2.4.0, I think a lot of the issues around this have been fixed. The I believe the jetty transport will now properly update the WSDL. Not 100% sure on that.
However, you can also configure in an endpoint property of "publishedEndpointUrl" to be the full URL of what you want exposed for that endpoint. Dan On Friday 22 April 2011 2:01:02 AM ext2 wrote: > Hi: > I am using cxf's jetty transport. > > Because I don't know the real ip where the webservice will be deploy > to, so I always configured the jaxws-endpoint with ip "127.0.0.1" in the > spring. And configure the http-engine to bind to any ip available; > > But unfortunately , at runtime, if I request the wsdl using the real > ip , the endpoint in the wsdl is always "127.0.0.1" , but not the real ip > of server; > For example, if I request wsdl throw > http://some-real-ip:8081/test?wsdl or > http://server-host-name:8081/test?wsdl > > The response wsdl 's endpoint will always be : > <soap:address location="http://localhost:8081/test "/> > > Could CXF replace the endpoint's host with the request url's host? > > > Thanks any suggestion -- Daniel Kulp [email protected] http://dankulp.com/blog Talend - http://www.talend.com
