Uploaded image for project: 'Karaf'
  1. Karaf
  2. KARAF-2201

http, war, and http-whiteboard feature should use the version of underlying pax-web feature

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.3.0
    • Fix Version/s: 2.4.0, 3.0.0
    • Labels:
      None
    • Environment:

      Karaf 2.3.0, Pax Web 1.1.12

      Description

      Pax Web 1.1.12 features:

      [uninstalled] [7.6.2.v20120308     ] jetty                                 org.ops4j.pax.web-1.1.12  
      [installed  ] [1.1.12              ] http                                  org.ops4j.pax.web-1.1.12  
      [installed  ] [1.1.12              ] war                                   org.ops4j.pax.web-1.1.12  
      

      Karaf 2.3.0's :

      [installed  ] [7.6.7.v20120910     ] jetty                                 karaf-2.3.0               Provide Jetty engine support
      [uninstalled] [2.3.0               ] http                                  karaf-2.3.0               Implementation of the OSGi HTTP service
      [uninstalled] [2.3.0               ] http-whiteboard                       karaf-2.3.0               Provide HTTP Whiteboard pattern support
      [uninstalled] [2.3.0               ] war                                   karaf-2.3.0               Turn Karaf as a full WebContainer
      

      Pax Web 1.1.12's http & war is actually newer, but is "older" than old Karaf 2.3.0's because of the version.

      This raises problems when trying to install webconsole, cxf, or other features that require http / war, because it will install the older (i.e. 2.3.0) version of http & war, not the newer 1.1.12.

      Karaf (2.3.1) should use the pax web feature version (i.e. 1.1.12) and not the Karaf version, so that upgrade pax web will be easier.

      Original ticket: http://team.ops4j.org/browse/PAXWEB-503

        Issue Links

          Activity

          Hide
          achim_nierbeck Achim Nierbeck added a comment -

          To my understanding this is a "api-breaking" change so this could only be addressed with Karaf 3.0 (which is already done )
          For the 2.x line we might consider this to work with 2.4.x but never for 2.3.x again because of a "breaking" change

          Show
          achim_nierbeck Achim Nierbeck added a comment - To my understanding this is a "api-breaking" change so this could only be addressed with Karaf 3.0 (which is already done ) For the 2.x line we might consider this to work with 2.4.x but never for 2.3.x again because of a "breaking" change
          Hide
          achim_nierbeck Achim Nierbeck added a comment -

          already fixed ...

          Show
          achim_nierbeck Achim Nierbeck added a comment - already fixed ...

            People

            • Assignee:
              Unassigned
              Reporter:
              ceefour Hendy Irawan
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development