[
https://jira.jboss.org/browse/JBOSGI-354?page=com.atlassian.jira.plugin.s...
]
David Bosschaert commented on JBOSGI-354:
-----------------------------------------
This issue was specifically related to the MC deployment behaviour. It doesn't apply
to the MSC-based OSGi framework.
Initial Bundle Start Level initialization is done in the wrong
place.
---------------------------------------------------------------------
Key: JBOSGI-354
URL:
https://jira.jboss.org/browse/JBOSGI-354
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: David Bosschaert
Assignee: David Bosschaert
Fix For: JBossOSGi 1.0.0 Beta9
Currently the initial bundle start level is set when bundle.start() is called. This is
really too late. You want to know the initial start level when the bundle got installed.
There is a test case failure for this, for which a temp workaround has been put into
place. The failing test is:
http://github.com/jbosgi/jbosgi/blob/master/testsuite/functional/src/test...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira