Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-6687

Some of the cxf bundles failed to export its OSGi service from CXF 3.1.4

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 3.1.4
    • Fix Version/s: None
    • Component/s: OSGi
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      Description

      From cxf 3.1.4, most of the bundles with setting lazy activation in the MANIFEST

      Bundle-ActivationPolicy = lazy
      

      This works well for Export-packages, but not work for Export-Service.

      103 | Starting |  40 | 3.1.4                   | Apache CXF Runtime JAX-RS Frontend
      104 | Active   |  40 | 3.1.4                   | Apache CXF Runtime Management
      105 | Starting |  40 | 3.1.4                   | Apache CXF JAX-RS Client
      106 | Starting |  40 | 3.1.4                   | Apache CXF JAX-RS Extensions: Providers
      107 | Starting |  40 | 3.1.4                   | Apache CXF JAX-RS Extensions: Search
      108 | Starting |  40 | 3.1.4                   | Apache CXF RS XML Security
      109 | Starting |  40 | 3.1.4                   | Apache CXF JAX-RS Service Description
      110 | Starting |  40 | 3.1.4                   | Apache CXF Runtime Security functionality
      

      For example, when deploy a customer application with jaxrs:server in the blueprint.xml, then it is waiting for namespace handlers http://cxf.apache.org/blueprint/jaxrs until failed to start.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                cschneider Christian Schneider
                Reporter:
                xldai Xilai Dai
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: