Mailing-List: contact dev-help@aries.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aries.apache.org
Date: Mon, 21 Feb 2011 10:24:38 +0000 (UTC)
From: "Guillaume Nodet (JIRA)" <jira@apache.org>
To: dev@aries.apache.org
Message-ID: 
 <812303540.5501.1298283878485.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <768047.298661294786729204.JavaMail.jira@thor>
Subject: [jira] Resolved: (ARIES-536) Have a way to specify a blueprint
 bundle should be started in sync with the start level service as much as
 possible
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Guillaume Nodet resolved ARIES-536.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: blueprint-0.4.0

> Have a way to specify a blueprint bundle should be started in sync with the start level service as much as possible
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-536
>                 URL: https://issues.apache.org/jira/browse/ARIES-536
>             Project: Aries
>          Issue Type: New Feature
>          Components: Blueprint
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
>             Fix For: blueprint-0.4.0
>
>
> The use case is for ordering startup using start-level.  If you have a bundle that has an optional dependency on a service provided by blueprint, you have no way to raise the chances that the service will be used from the start as blueprint bundles are started asynchronously.
> I'd like to have a way to specifiy that the blueprint bundle should be started asynchronously, at least until a GRACE_PERIOD event would be fired, in which case, the remaning things would be done asynchronously.
> This definitely should not be used as a way to work around bad bundle behaviors that aren't resiliant with missing dependencies, but really to ensure that when the server boots up, services are started in an optimal order (log and  configadmin should be started before the other ones if possible).

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira