I ended up writing an internal router to solve this. You can setup a jetty listener on the port you want and read the URL to determine which internal port to route the message to. So internally I use ports 9191 - 9196 for various services and just send requests internally to those after determined destination based off URL, which I have mapped in a properties file.
On Thu, Feb 19, 2015 at 6:35 AM, jjathman [via Camel] < [email protected]> wrote: > Is this still the case? I was hoping to have a CXF web service as well as > a Jetty Rest endpoint using the new rest DSL in Camel 2.14. Is there any > way to reuse the Jetty server? I would rather not have multiple ports for a > single JVM. > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://camel.465427.n5.nabble.com/Port-already-in-use-when-using-CXF-consumer-and-jetty-tp5714378p5762911.html > To unsubscribe from Port already in use when using CXF consumer and > jetty, click here > <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5714378&code=ZXJpYy5iZW5kZXJAZ21haWwuY29tfDU3MTQzNzh8LTQyNDU1Njk2Mg==> > . > NAML > <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://camel.465427.n5.nabble.com/Port-already-in-use-when-using-CXF-consumer-and-jetty-tp5714378p5762918.html Sent from the Camel - Users mailing list archive at Nabble.com.
