camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <>
Subject [jira] Commented: (CAMEL-1530) Upgrade camel-http to use httpclient 4.0
Date Mon, 04 Jan 2010 15:12:15 GMT


Oleg Kalnichevski commented on CAMEL-1530:


> I think we can't use the method HttpProtocolParamBean.setVersion(HttpVersion), because
HttpVersion is not a String or primitive

I am not entirely sure why this is a problem. Why could not you just use a custom PropertyEditor
to convert from String to HttpVersion, if you are using Spring DI, or similar mechanism, if
you are using some other DI framework? I personally think this would make for a much cleaner

> But what is with the other 26 HTTP client params? Should/Could we contribute ParamBean's
for these params to the httpclient project?

You might be better off maintaining a small number of parameter beans for those parameters
Camel cares about within the project. Alternatively we could consider starting an optional
httpclient-spring or httpclient-di module within HC for Spring / DI specific classes.


> Upgrade camel-http to use httpclient 4.0
> ----------------------------------------
>                 Key: CAMEL-1530
>                 URL:
>             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.

View raw message