[
https://issues.apache.org/activemq/browse/CAMEL-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57785#action_57785
]
Claus Ibsen commented on CAMEL-1530:
------------------------------------
@Christian
The {{/<camel_root>/tests}} have not been patched.
I frankly deleted the http related tests as they where configuring HTTP Client
from Spring XML.
This is easy to do in 3.1 but *hard* to do in 4.0.1.
For example changing the default max 2 connections per connection to eg 5
requires a lot more work according to
http://hc.apache.org/httpcomponents-client/tutorial/html/connmgmt.html#d4e558
@Oleg
I wonder why you must provide a SchemeRegistry to the
ThreadSafeClientConnectionManager etc.? Is it not possible to let it default
create its own registry using http port 80 and https at 443.? I see a
convention over configuration win there?
http://hc.apache.org/httpcomponents-client/tutorial/html/connmgmt.html#d4e558
Maybe I missed something but I only used 10 min to browse the docu and all the
examples I saw was pure Java configured examples.
> 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
>
> Attachments: camel-gae_20100211.patch, camel-http.zip,
> camel-http_20100211.patch, camel-jetty.zip, camel-jetty_20100211.patch,
> camel-servlet_20100211.patch, localhost.ks
>
> Time Spent: 4 weeks
> Remaining Estimate: 0 minutes
>
> 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.
