I think it does make a lot of sense to have a camel-http5 component which would also have the side effect to make the "http" scheme available for the Java Http client in the future.
So +1 for me --- Luca Burgazzoli On Sun, Mar 22, 2020 at 12:55 PM Andrea Cosentino <anco...@gmail.com> wrote: > Hello Pascal, > > Personally I think it makes sense to support HttpComponents 5, this time we > won't have to deal with OSGi stuff, because they're not supporting it. > > So, unless Karaf will release the OSGi bundles for these jars, we'll have > to make it work only on plain camel and SB. > > Eventually when we'll switch to the JDK http client, we can always have > also the other alternative, the http5 one. > > So +1 for me. > > Thanks > > Il giorno dom 22 mar 2020 alle ore 12:40 Pascal Schumacher < > pascalschumac...@gmx.net> ha scritto: > > > Hi, > > > > Apache HttpComponents Client 5.0 was released last month (see: > > https://hc.apache.org/news.html). > > > > Package names and a lot of class and method names were changed. > > > > As Camel allows users to customize Http Client usage and this exposes > > Http Client 4 classes, I believe a new component should be created > > (instead of updating the existing one). > > > > I started to have a look at creating an new http5 component based on > > Apache Http Client 5 (not sure if I would be able to do it) . > > > > When camel moves to Java 11 (not sure when that will be) there are plans > > to implement an http component based on the Java (JDK) http client (see: > > https://issues.apache.org/jira/browse/CAMEL-14660). > > > > So the question is: Does it make sense to invest more time into this or > > is it a waste of time? > > > > What do you think? > > > > -Pascal > > > > > > > > > > > > > > >
