I don't know, but step #2 and step #3 of my JUnit test case samples have general solutions for embedded Tomcat and embedded Jetty: http://www.jroller.com/gmazza/entry/writing_junit_test_cases_for
With the general solutions of either above, you might be able to programmatically work with Tomcat and Jetty (instead of doing this configuration within CXF) to get it to listen to only a particular URL. If so, the Tomcat or Jetty user's list can probably be helpful for you here. Glen Henning, Mark - AES wrote: > > Good Day, > > We are developing an application that needs to be able to lock down the > embedded jetty server to listen _ONLY_ to packets on 127.0.0.1. > I have looked through the documentation and have not found what I'm > looking for. The server is started with the code below: > -- View this message in context: http://www.nabble.com/Constraining-Stand-alone-Embedded-Jetty-service-address-in-code-tp21813633p21820078.html Sent from the cxf-user mailing list archive at Nabble.com.
