[
https://issues.apache.org/activemq/browse/CAMEL-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56618#action_56618
]
Oleg Kalnichevski commented on CAMEL-1530:
------------------------------------------
@Claus
> The API in 4.0 is changed a bit / a fair bit AFAIR when I took a initial stab
> at upgrading the camel-http to 4.0. So I turned back at that time.
The API in 4.0 was meant to change 'a fair bit' because the old core components
dated back to the HttpClient 1.0 days had degraded into an utter
incomprehensible mess no one was willing to maintain / work with.
> So I wonder if backwards comparability is really preserved anyway?
No, it was not, because it was not meant to. HttpClient 4.0 was meant to be a
complete ground-up rewrite. This was a collective decision of HC maintainers
made as early as year 2004 (well before HttpClient 2.0 went final)
> Anyway I think having unfriendly DI configuration is a major mistake as a lot
> of users use it to configure and wire their apps.
Like it was a major mistake to not have hierarchical configuration back in 2004
to some people. I cannot make everyone happy, can I? The biggest problem is
always the most immediate one.
Anyways, it is fairly easy to wire up HTTP params with Spring when using
parameter beans. It is even easier with Guice
Oleg
> 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.
