[
https://issues.apache.org/jira/browse/FELIX-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215539#comment-13215539
]
Felix Meschberger commented on FELIX-3361:
------------------------------------------
If start levels come into play the StartLevel service dictates the actual
bundle states.
> * when the bundle start level is greater than the framework target start
> level
The bundle is not expected to start until the framework start level is
increased to at least the bundle's start level. Start levels are increased
step-wise. So if a bundle is at 5, the current is 2 and the target is 6, the
start level is increased to 3, 4, 5, and 6 and bundles assigned to the
respective start levels are actually started.
Thus a bundle at level x with the framework start level being y < x will at
most be in the RESOLVED state.
* if the start level thread is already running
Right, if the start level is being increased, the bundle is only actually
started when passing the bundle's start level.
Bundle.start in these situations will only persistently mark the bundle started
(for later start level operations to actually start the bundle).
> 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
