Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.0
    • Component/s: None
    • Labels:
      None

      Description

      As Apache CXF 2.3.0 has been released, we can now support it.

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        1d 14h 1m 1 Freeman Fang 13/Oct/10 11:49
        Jeff Turner made changes -
        Project Import Sat Nov 27 01:13:56 EST 2010 [ 1290838436878 ]
        Gert Vanthienen made changes -
        Fix Version/s 4.4.0 [ 12241 ]
        Fix Version/s 4.3.0 [ 12345 ]
        Freeman Fang made changes -
        Fix Version/s 4.4.0 [ 12241 ]
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Show
        Freeman Fang added a comment - commit fix http://svn.apache.org/viewvc?rev=1022065&view=rev
        Freeman Fang made changes -
        Assignee Freeman Fang [ ffang ]
        Jean-Baptiste Onofré made changes -
        Field Original Value New Value
        Summary Upgrade to CXF 2.3.0 Upgrade to CXF 2.2.11
        Hide
        Jean-Baptiste Onofré added a comment -

        As Camel 2.5.0 will use CXF 2.2.11, we upgrade first to CXF 2.2.11 (for the SMX 4.3).

        Camel 2.6 will use CXF 2.3, that will be included in SMX 4.4.

        Show
        Jean-Baptiste Onofré added a comment - As Camel 2.5.0 will use CXF 2.2.11, we upgrade first to CXF 2.2.11 (for the SMX 4.3). Camel 2.6 will use CXF 2.3, that will be included in SMX 4.4.
        Hide
        Daniel Kulp added a comment -

        I don't see any reason to NOT upgrade to 2.3.0. It isn't any bigger of a deal than going from Camel 2.4.0 to 2.5.0. It's a point release. If you are updating Camel, updating CXF as well should be just as fine. There are PLENTY of use cases of using CXF services in ServiceMix that don't involve camel. We should be able to provide those users with the new functionality.

        Show
        Daniel Kulp added a comment - I don't see any reason to NOT upgrade to 2.3.0. It isn't any bigger of a deal than going from Camel 2.4.0 to 2.5.0. It's a point release. If you are updating Camel, updating CXF as well should be just as fine. There are PLENTY of use cases of using CXF services in ServiceMix that don't involve camel. We should be able to provide those users with the new functionality.
        Hide
        Freeman Fang added a comment -

        Hi JB,

        I'm not so keen to upgrade to cxf 2.3.0 now, as cxf 2.3.0 is a big release and AFAIK the continuation API changes which will affect our smx-cxf consumer asyn invocation.
        Also camel 2.5.0 which will be released very soon still use cxf 2.2.11(as cxf continuation API also affect camel-cxf), camel 3.0 which should be released at 2011 Q1 plan to use cxf 2.3, we should keep on same page with Camel.
        So let's upgrade to cxf 2.2.11 for now.
        I'll create related issues and work on it.

        Best Regards

        Freeman

        Show
        Freeman Fang added a comment - Hi JB, I'm not so keen to upgrade to cxf 2.3.0 now, as cxf 2.3.0 is a big release and AFAIK the continuation API changes which will affect our smx-cxf consumer asyn invocation. Also camel 2.5.0 which will be released very soon still use cxf 2.2.11(as cxf continuation API also affect camel-cxf), camel 3.0 which should be released at 2011 Q1 plan to use cxf 2.3, we should keep on same page with Camel. So let's upgrade to cxf 2.2.11 for now. I'll create related issues and work on it. Best Regards Freeman
        Jean-Baptiste Onofré created issue -

          People

          • Assignee:
            Freeman Fang
            Reporter:
            Jean-Baptiste Onofré
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development