camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: Camel Jetty component and overlapping urls when a consumer
Date Sat, 21 Dec 2013 06:56:29 GMT
No you are correct, the camel-jetty component can share the same port
across bundles.

On Sat, Dec 21, 2013 at 1:52 AM, samslara <> wrote:
> It was my understanding of the contrary.  I'm currently using servicemix
> where there are 20+ bundles each with a camel context and each of those with
> routes starting with a jetty consumer (eg: <from
> uri="jetty:http:" />).  We haven't had any problems with
> each of these camel routes listening on the common 8080 port.  In fact each
> of these routes are differentiated by a different context path (eg:
> jetty: vs jetty: and it all seems
> to route correctly.  Also with current versions of servicemix there is a
> commons configuration of jetty.xml which I believed to be the configuration
> of the common jetty server for all inbound <from uri="jetty:..." />
> requests.
> I thought the jetty Camel Component is able to do this via a single jetty
> server that is started up on servicemix and where each bundle (via the jetty
> Camel Component) registers a CamelContinuationServlet.  Am I wrong with any
> of this?
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

Claus Ibsen
Red Hat, Inc.
Twitter: davsclaus
Author of Camel in Action:
Make your Camel applications look hawt, try:

View raw message