Return-Path: 
 <issues-return-10699-apmail-karaf-issues-archive=karaf.apache.org@karaf.apache.org>
X-Original-To: apmail-karaf-issues-archive@minotaur.apache.org
Delivered-To: apmail-karaf-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 3CBA5DC3D
	for <apmail-karaf-issues-archive@minotaur.apache.org>;
 Sun, 23 Sep 2012 18:00:08 +0000 (UTC)
Received: (qmail 35419 invoked by uid 500); 23 Sep 2012 18:00:08 -0000
Delivered-To: apmail-karaf-issues-archive@karaf.apache.org
Received: (qmail 35385 invoked by uid 500); 23 Sep 2012 18:00:07 -0000
Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@karaf.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@karaf.apache.org>
List-Post: <mailto:issues@karaf.apache.org>
List-Id: <issues.karaf.apache.org>
Reply-To: dev@karaf.apache.org
Delivered-To: mailing list issues@karaf.apache.org
Received: (qmail 35368 invoked by uid 99); 23 Sep 2012 18:00:07 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Sep 2012 18:00:07 +0000
Date: Mon, 24 Sep 2012 05:00:07 +1100 (NCT)
From: "Christian Schneider (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <428383989.114042.1348423207625.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <399704321.11166.1330678321190.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (KARAF-1245) blueprint deployer and spring
 deployer should get started before features.core bundle
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/KARAF-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461471#comment-13461471 ] 

Christian Schneider commented on KARAF-1245:
--------------------------------------------

I think the feature install now waits for some time for missing url handlers. Does this fix the problem? I am also working on parallelizing the install of bundles. This will help if the url handler appear after a bundle they should install. See kARAf-608. I will explain what I have in mind there shortly.
                
> blueprint deployer and spring deployer should get started before features.core bundle
> -------------------------------------------------------------------------------------
>
>                 Key: KARAF-1245
>                 URL: https://issues.apache.org/jira/browse/KARAF-1245
>             Project: Karaf
>          Issue Type: Improvement
>            Reporter: Freeman Fang
>            Assignee: Ioannis Canellos
>             Fix For: 2.2.6, 3.0.0
>
>
> When org.apache.karaf.features.core bundle is up, it will load features descriptors and try install features, however if the features descriptor has bundle like
> <bundle>blueprint:file:etc/some-blueprint.xml</bundle>, we need blueprint url handler available in the OSGi container, so we need blueprint deployer and spring deployer get started before features.core bundle

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira