[ 
https://issues.apache.org/activemq/browse/CAMEL-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56611#action_56611
 ] 

Oleg Kalnichevski commented on CAMEL-1530:
------------------------------------------

> Jesus this tops the most unfriendly configuration I have seen in long time. 

DI framework unfriendly, maybe. However, this configuration API enables 
consumers of HttpClient services (1) selectively override client level settings 
at the request level and (2) introduce new or user defined parameters without 
breaking API compatibility

If you can think of a better approach that is more DI framework friendly while 
still allowing for 1 and 2, I would be in your debt

> Wonder ever if they think that is easy to wire up with Spring XML ?

Have you looked at the parameter bean classes?

http://hc.apache.org/httpcomponents-client/tutorial/html/fundamentals.html#d4e327

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.2.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.

Reply via email to