[
https://issues.apache.org/activemq/browse/CAMEL-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56615#action_56615
]
Claus Ibsen commented on CAMEL-1530:
------------------------------------
@Christian, @Oleg
@Oleg thank for the link.
> HttpClient includes a number of bean classes that can used in order to
> initialize HttpParams objects using standard Java bean conventions.
This sounds interesting.
If we could know how many of these beans are, then we could use the Camel API
to set those values automatic using its Introspection API.
Then I think we do not have the problem in camel with the _not so nice
solution_ that Christian had to do.
Something like in HttpComponent in the createEndpoint method. Then we should be
good to go.
{code}
HttpClientParams clientParams = new HttpClientParams();
IntrospectionSupport.setProperties(new HttpProtocolParamBean(params),
parameters, "httpClient.");
IntrospectionSupport.setProperties(new HttpSomeOtherParamBean(params),
parameters, "httpClient.");
IntrospectionSupport.setProperties(new HttpAndAnotherParamBean(params),
parameters, "httpClient.");
{code}
> 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.
