Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 420A0183B2 for ; Mon, 23 Nov 2015 15:10:11 +0000 (UTC) Received: (qmail 28766 invoked by uid 500); 23 Nov 2015 15:10:11 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 28732 invoked by uid 500); 23 Nov 2015 15:10:11 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 28715 invoked by uid 99); 23 Nov 2015 15:10:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Nov 2015 15:10:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id E86992C1F56 for ; Mon, 23 Nov 2015 15:10:10 +0000 (UTC) Date: Mon, 23 Nov 2015 15:10:10 +0000 (UTC) From: "Christian Schneider (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CXF-6687) Some of the cxf bundles failed to export its OSGi service from CXF 3.1.4 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CXF-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved CXF-6687. -------------------------------------- Resolution: Won't Fix The issue was in karaf so I set to wont fix in CXF. > Some of the cxf bundles failed to export its OSGi service from CXF 3.1.4 > ------------------------------------------------------------------------ > > Key: CXF-6687 > URL: https://issues.apache.org/jira/browse/CXF-6687 > Project: CXF > Issue Type: Bug > Components: OSGi > Affects Versions: 3.1.4 > Reporter: Xilai Dai > Assignee: Christian Schneider > > From cxf 3.1.4, most of the bundles with setting lazy activation in the MANIFEST > {code} > Bundle-ActivationPolicy = lazy > {code} > This works well for Export-packages, but not work for Export-Service. > {code} > 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 > {code} > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)