[ http://issues.apache.org/jira/browse/FELIX-168?page=all ]
Felix Meschberger updated FELIX-168:
------------------------------------
Attachment: FELIX-168.diff
Attached is a patch, which (a) calls the StartLevelImpl.setStartLevelAndWait
method when raising the start level to the beginning start level and (b) does
not broadcast the START_LEVEL_CHANGED event if the framework is not running.
> Start Level Service: 8.2.3 Startup Sequence error
> -------------------------------------------------
>
> Key: FELIX-168
> URL: http://issues.apache.org/jira/browse/FELIX-168
> Project: Felix
> Issue Type: Bug
> Components: Specification compliance, Framework
> Affects Versions: 0.8.0
> Reporter: Felix Meschberger
> Attachments: FELIX-168.diff
>
>
> Section 8.2.3, Startup Sequence, of the Start Level Service specification
> states, that the Framework must raise the start level to the beginning start
> level as if calling StartLevel.setStartLevel with one exceptions: When the
> beginning start level has been reached, a FrameworkEvent.STARTED event must
> be broadcast instead of a FrameworkEvent.START_LEVEL_CHANGED.
> In conjunction with Section 4.7.1, Statup, of the Life Cycle Layer
> specification, I assume that (a) the start level must be reached before the
> framework can be assumed to have started and (b) that the system bundle only
> enters the ACTIVE state after the beginning start level has been reached.
> If this assumption would be correct, two issues exist in the Felix class: (a)
> the start level is raised asynchronously, meaning that the
> FrameworkEvent.STARTED is broadcast before the beginning start level has been
> reached and (b) when reaching the beginning start level a
> FrameworkEvent.START_LEVEL_CHANGED is sent, which should not actually be done.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
