camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: [discuss] Future of the camel-jetty producer side
Date Mon, 08 Dec 2014 16:25:47 GMT
On Mon, Dec 8, 2014 at 5:17 PM, Christian Schneider
<> wrote:
> There are some changes we need to do in camel to support the upcoming karaf
> 4. The most visible difference is that karaf 4 will include jetty 9.
> Recently Dan migrated the camel-jetty component to support jetty 8 and 9 on
> the consumer side. The consumer should be solved for the most part.
> On the client side jetty changed a lot more though so it is difficult to
> support jetty 8 and 9 with the same client code. So I think we have some
> options here:
> 1. Split up the jetty component into a module for the server side that
> supports jetty 8 and 9 and separate components for the client side for jetty
> 8 and 9 respectively


> 2. Have separate jetty components for each major version of jetty


this is what we do for other components.
allows to have compile time over reflection hacks.

> 3. Remove the jetty producer side as most people use camel-http or
> camel-http4 anyway


No there is actually people that uses jetty for proxying, eg from
jetty -> to jetty where jetty continuations and whatnot comes in play.

> I personally would go for option 3 as we have a lot of http components
> already and I don't think many people used jetty as a producer.
> Another argument for it is that the next major version of jetty will
> probably be largely incompatible again. So it would be good to have less
> exposure to jetty apis.
> Christian
> --
> Christian Schneider
> Open Source Architect

Claus Ibsen
Red Hat, Inc.
Twitter: davsclaus
Author of Camel in Action:

View raw message