Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Date: Fri, 24 Feb 2012 09:59:48 +0000 (UTC)
From: "Guillaume Nodet (Updated) (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Message-ID: 
 <559102249.14800.1330077588735.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1143995325.14781.1330077108761.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (FELIX-3361) Bundle#start does not comply with the
 spec
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Guillaume Nodet updated FELIX-3361:
-----------------------------------

    Description: 
The spec says:  "When the start method returns without an exception, the state of the bundle will either be ACTIVE or STARTING, depending on the declared activation policy and whether it was used. If the start method throws an exception, then the bundle will not be in either of these states and the stop method will not be called for this Bundle Activator instance."

However there is a case where this does not happen, which is when the start level thread is already running
I think the Bundle#start should either activate the bundle or wait for the bundle to be activated before returning in order to comply with the spec. 


  was:
The spec says:  "When the start method returns without an exception, the state of the bundle will either be ACTIVE or STARTING, depending on the declared activation policy and whether it was used. If the start method throws an exception, then the bundle will not be in either of these states and the stop method will not be called for this Bundle Activator instance."

However there are cases where this does not happen:
 * when the bundle start level is greater than the framework target start level
 * if the start level thread is already running
I think the Bundle#start should either activate the bundle or wait for the bundle to be activated before returning in order to comply with the spec. 

    
> Bundle#start does not comply with the spec
> ------------------------------------------
>
>                 Key: FELIX-3361
>                 URL: https://issues.apache.org/jira/browse/FELIX-3361
>             Project: Felix
>          Issue Type: Bug
>    Affects Versions: framework-4.0.2
>            Reporter: Guillaume Nodet
>
> The spec says:  "When the start method returns without an exception, the state of the bundle will either be ACTIVE or STARTING, depending on the declared activation policy and whether it was used. If the start method throws an exception, then the bundle will not be in either of these states and the stop method will not be called for this Bundle Activator instance."
> However there is a case where this does not happen, which is when the start level thread is already running
> I think the Bundle#start should either activate the bundle or wait for the bundle to be activated before returning in order to comply with the spec. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira