You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/04/02 14:47:08 UTC

[jira] Created: (CAMEL-2608) Restore the old camel-http as Apache Http Client 4.0.1 does not cover same feature set as 3.1

Restore the old camel-http as Apache Http Client 4.0.1 does not cover same feature set as 3.1
---------------------------------------------------------------------------------------------

                 Key: CAMEL-2608
                 URL: https://issues.apache.org/activemq/browse/CAMEL-2608
             Project: Apache Camel
          Issue Type: Task
          Components: camel-http
            Reporter: Claus Ibsen
             Fix For: 2.3.0


For example some options to setup auth and proxies are missing in 4.0.1 which was avail in 3.1. They seems to be added in 4.1. But 4.1 is on a long release as its alpha2 currently.
And to also allow a slowly migration path for existing Camel users we should let camel-http be using http client 3.1.

- camel-http -> camel-http4 (component should be named http4)
- restore old camel-http
- camel-jetty should use http4 for testing and it should extend camel-http4 as its code base have been adjusted as well



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-2608) Restore the old camel-http as Apache Http Client 4.0.1 does not cover same feature set as 3.1

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58751#action_58751 ] 

Claus Ibsen commented on CAMEL-2608:
------------------------------------

trunk: 932710.

Adjusted features.xml

> Restore the old camel-http as Apache Http Client 4.0.1 does not cover same feature set as 3.1
> ---------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-2608
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2608
>             Project: Apache Camel
>          Issue Type: Task
>          Components: camel-http
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.3.0
>
>
> For example some options to setup auth and proxies are missing in 4.0.1 which was avail in 3.1. They seems to be added in 4.1. But 4.1 is on a long release as its alpha2 currently.
> And to also allow a slowly migration path for existing Camel users we should let camel-http be using http client 3.1.
> - camel-http -> camel-http4 (component should be named http4)
> - restore old camel-http
> - camel-jetty should use http4 for testing and it should extend camel-http4 as its code base have been adjusted as well

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (CAMEL-2608) Restore the old camel-http as Apache Http Client 4.0.1 does not cover same feature set as 3.1

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58750#action_58750 ] 

Claus Ibsen commented on CAMEL-2608:
------------------------------------

trunk: 932707, 932709.

Fixed tests in camel-itest and restored some http client 3.1 tests in camel-itest

> Restore the old camel-http as Apache Http Client 4.0.1 does not cover same feature set as 3.1
> ---------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-2608
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2608
>             Project: Apache Camel
>          Issue Type: Task
>          Components: camel-http
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.3.0
>
>
> For example some options to setup auth and proxies are missing in 4.0.1 which was avail in 3.1. They seems to be added in 4.1. But 4.1 is on a long release as its alpha2 currently.
> And to also allow a slowly migration path for existing Camel users we should let camel-http be using http client 3.1.
> - camel-http -> camel-http4 (component should be named http4)
> - restore old camel-http
> - camel-jetty should use http4 for testing and it should extend camel-http4 as its code base have been adjusted as well

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (CAMEL-2608) Restore the old camel-http as Apache Http Client 4.0.1 does not cover same feature set as 3.1

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58752#action_58752 ] 

Claus Ibsen commented on CAMEL-2608:
------------------------------------

TODO: Update release notes page
TODO: Add http4 components page
TODO: Adjust http components page

> Restore the old camel-http as Apache Http Client 4.0.1 does not cover same feature set as 3.1
> ---------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-2608
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2608
>             Project: Apache Camel
>          Issue Type: Task
>          Components: camel-http
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.3.0
>
>
> For example some options to setup auth and proxies are missing in 4.0.1 which was avail in 3.1. They seems to be added in 4.1. But 4.1 is on a long release as its alpha2 currently.
> And to also allow a slowly migration path for existing Camel users we should let camel-http be using http client 3.1.
> - camel-http -> camel-http4 (component should be named http4)
> - restore old camel-http
> - camel-jetty should use http4 for testing and it should extend camel-http4 as its code base have been adjusted as well

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Resolved: (CAMEL-2608) Restore the old camel-http as Apache Http Client 4.0.1 does not cover same feature set as 3.1

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-2608.
--------------------------------

    Resolution: Fixed

> Restore the old camel-http as Apache Http Client 4.0.1 does not cover same feature set as 3.1
> ---------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-2608
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2608
>             Project: Apache Camel
>          Issue Type: Task
>          Components: camel-http
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.3.0
>
>
> For example some options to setup auth and proxies are missing in 4.0.1 which was avail in 3.1. They seems to be added in 4.1. But 4.1 is on a long release as its alpha2 currently.
> And to also allow a slowly migration path for existing Camel users we should let camel-http be using http client 3.1.
> - camel-http -> camel-http4 (component should be named http4)
> - restore old camel-http
> - camel-jetty should use http4 for testing and it should extend camel-http4 as its code base have been adjusted as well

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.