[
https://issues.apache.org/activemq/browse/CAMEL-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56634#action_56634
]
Claus Ibsen commented on CAMEL-1530:
------------------------------------
@Oleg
I have much respect for the bold move to do a group-up rewrite. That is
fantastic that you guys had the commitment to do that. Often a framework of the
size of HTTP could have been large and thus much work to do.
That makes much sense that upgrading from 3.1 to 4.0 does take a bit of work on
our side as well :)
> Anyways, it is fairly easy to wire up HTTP params with Spring when using
> parameter beans. It is even easier with Guice
Yeah those beans seems to help. Wonder though if you could have one bean for
all configurations, but I guess maybe that leads to one to _giant_ bean?
Thanks for the help, lets hope that Christian can use those beans to much
easier configure HTTP Client from the free from URI parameters on the Camel
endpoint.
> Upgrade camel-http to use httpclient 4.0
> ----------------------------------------
>
> Key: CAMEL-1530
> URL: https://issues.apache.org/activemq/browse/CAMEL-1530
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-http
> Affects Versions: 2.0-M1
> Reporter: Claus Ibsen
> Assignee: Christian Mueller
> Fix For: 2.3.0
>
>
> Upgrading httpclient from 3.1 to 4.0 requires changes in the camel-http code
> as the API has change quite a lot.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
