Jetty is known and best used for their HTTP Server. Not their http client which are "not so good" and not really a high priority of that company of Jetty.
The jetty consumer is not deprecated, its only the producer (using Camel lingo). On Wed, Apr 26, 2017 at 5:42 PM, Zoran Regvart <[email protected]> wrote: > Hi Sebastian, > speaking from my experience, the reasoning behind the decision to > deprecate Jetty producer has to do with the amount of work needed keep > up with Jetty changes. > > As an illustration take a look at the number of upgrade Jetty issues > on the Camel JIRA[1]. Some of those issues were upgrades of minor > Jetty versions that introduced braking changes in public API. > > I think that going forward you can rely on HTTP Components v4 (http4 > component) as it has a proven track record and we can easily keep up > with any changes there. Not to mention that it's a Apache Foundation > project so within our garden. > > Undertow producer is not par with features of http4 producer at the > moment, but will be of significance once it has matured a bit more. > > zoran > > [1] > https://issues.apache.org/jira/browse/CAMEL-2402?jql=project%20%3D%20CAMEL%20AND%20text%20~%20%22upgrade%20jetty%22 > > On Mon, Apr 24, 2017 at 12:55 PM, sbrandt2 <[email protected]> wrote: >> With the jetty producer surprisingly being deprecated recently via >> CAMEL-10998 I (and probably a lot of other users) are now in the situation >> having to plan the migration to another http producer. >> I'd also like to avoid being in the same situation again in some months >> having to migrate again. >> >> Given the choice of available http related components, I'd like to ask Camel >> developers for guidance on which http component(s) will be the "main" long >> time supported http stack for Camel. >> >> For producer endpoints, the choice would probably be between: http4, >> netty4-http, undertow >> For consumer endpoints: jetty, netty4-http, undertow >> >> I'm aware of the dynamics of open source projects, but given the importance >> of actively developed and supported http producer/consumer endpoints for an >> integration framework I believe an answer is valuable to Camel users. >> >> Also, to assess the urgency of a migration away from jetty producer >> endpoint, it would be helpful to know if there are serious issues with it. >> The description in CAMEL-10998 is a bit vague and I didn't find any >> discussion about the deprecation on the dev forum. >> >> Thank you! >> Sebastian >> >> >> >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/Guidance-to-choose-future-proof-http-consumer-producer-components-tp5798182.html >> Sent from the Camel - Users mailing list archive at Nabble.com. > > > > -- > Zoran Regvart -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
