Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: aries-dev@incubator.apache.org
Message-ID: <1262045986.1259789780774.JavaMail.jira@brutus>
Date: Wed, 2 Dec 2009 21:36:20 +0000 (UTC)
From: "Lin Sun (JIRA)" <jira@apache.org>
To: aries-dev@incubator.apache.org
Subject: [jira] Resolved: (ARIES-64) Have blueprint extender process bundles
 associated with composite bundle when detecting the CompositeBundleFactory
 service
In-Reply-To: <1800858677.1259789180685.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ARIES-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lin Sun resolved ARIES-64.
--------------------------

    Resolution: Fixed

verified by itest BlueprintContainer2BTCustomizerTest

> Have blueprint extender process bundles associated with composite bundle when detecting the CompositeBundleFactory service
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-64
>                 URL: https://issues.apache.org/jira/browse/ARIES-64
>             Project: Aries
>          Issue Type: Improvement
>          Components: Blueprint
>            Reporter: Lin Sun
>            Assignee: Lin Sun
>
> This is a follow on enhancement after Aries-51.  In Aries-51 we added code to process bundles associated with composite bundle when detecting composite bundle starting/active.
> This JIRA is about enhance the process of check existing bundles and bundles associated with composite bundles that were started before the blueprint bundle, if the composite bundle factory service is avail.   This JIRA also added an itest for this scenario that blueprint sample is started in a child framework, before we start the blueprint bundle.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.