[
https://issues.apache.org/jira/browse/FELIX-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215545#comment-13215545
]
Guillaume Nodet commented on FELIX-3361:
----------------------------------------
Yeah, but the second case is against the spec. I don't have any problem with
the fact that the actual start of the bundle is delegated to the start level
thread, however, the return value of Bundle#start should be deterministic and
that's not the case.
In that case, waiting for the bundle to be started by the start level thread
before returning should do the trick.
> 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
