Found the ticket. FWIW okhttp dependency is already there for the unit tests in camel-jetty9. https://issues.apache.org/jira/browse/CAMEL-9268
I just assigned to myself in case I have spare time, but it would be great if anyone else could make it before me. Thanks, Tomo On 03/29/2017 02:52 AM, Claus Ibsen wrote:
btw http4 is not the most easy http client to use and configure. I would love if we get a new camel http component based on okhttp. https://square.github.io/okhttp/ There should be a JIRA about this at Apache Camel. On Tue, Mar 28, 2017 at 7:31 PM, Claus Ibsen <[email protected]> wrote:You need to define a new http4 component if you have different client configurer. It can only use one, and the first one created. So create a new component with a different name, such as http4-foo, http4-bar etc. You can register new components in camel context.addComponent("http4-foo", new HttpComponent()); On Wed, Mar 22, 2017 at 11:23 PM, Abhishek.Jha09 <[email protected]> wrote:Hi all, Subject pretty much sums up my query. I have a route like from("direct:a").routeId("myroute") .toD("http4://localhost:8080/user/${headers.id}?httpClientConfigurer=myHttpConfigClient") I have set up "myHttpConfigClient" in SimpleRegistry in camel context. When I change the config values of this instance and add the route again to camel context, the config parameters don't change. However, if I do the same in a route created like below, without dynamic to, it works perfectly fine. from("direct:a").routeId("myroute") .to("http4://localhost:8080/user?httpClientConfigurer=myHttpConfigClient") Can anyone please help me with this? -- View this message in context: http://camel.465427.n5.nabble.com/Unable-to-update-httpclientconfigurer-instance-on-dynamic-to-endpoint-tp5795918.html Sent from the Camel - Users mailing list archive at Nabble.com.-- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
