[
https://issues.apache.org/jira/browse/FELIX-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215569#comment-13215569
]
Felix Meschberger commented on FELIX-3361:
------------------------------------------
See 8.3.5 Starting a Bundle:
If a bundle is started by calling the Bundle.startmethod, then the OSGi
Framework must mark the bundle as persistently started. The OSGi Framework must
not actually start a bundle when the active start level is less than the
bundle’s start level. In that case, the state must not change.
Also the Bundle.start(int) JavaDoc clarifies this.
> 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
