[
https://issues.apache.org/activemq/browse/CAMEL-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Mueller updated CAMEL-1530:
-------------------------------------
Attachment: camel-http.patch
camel-http-test.patch
@Claus,
as I wrote in one of my posts before, I think it's a good idea to have a good
test coverage in camel-http itself. Otherwise it's difficult to find the real
problem after we upgrade to httpclient 4.0 (because we have to change code in
camel-http and camel-jetty), if some tests in camel-jetty fail but all
camel-http tests succeed.
I started with some simple unit tests for the helper classes and I think I
found a bug in org.apache.camel.component.http.helper.GZIPHelper. I added a
patch file with unit test classes which show the problem. I also added a patch
file with a fix for this problem.
After that, I would like to start to write some tests like we have in
camel-ftps. We could start a local http test server and send our test requests
to this server. What do you think about this?
Regards,
Christian
> 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-http-test.patch, camel-http.patch
>
>
> 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.
