[jboss-osgi-issues] [JBoss JIRA] Commented: (JBOSGI-99) No explicit control over bundle.start()

[Thomas Diesler (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBOSGI-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12494421#action_12494421 ] 

Thomas Diesler commented on JBOSGI-99:
--------------------------------------

Reopened

The MC Framework incorrectly uninstalls the bundle if there is a failure in bundle.start()

The controller context reached its required stage DESCRIBED after bundle install. A subsequent call to bundle.start() is supposed to transition to stages CLASSLOADER and then INSTALLED, which corresponds to the Bundle states RESOLVED  and ACTIVE respectively.

If the transition to INSTALLED fails, the controller context gets undeployed, which causes the bundle to transition to UNINSTALLED.

The desired behaviour is:

* on fail to resolve: remain in state INSTALLED
* on fail to start: remain in state RESOLVED
  

> No explicit control over bundle.start()
> ---------------------------------------
>
>                 Key: JBOSGI-99
>                 URL: https://jira.jboss.org/jira/browse/JBOSGI-99
>             Project: JBoss OSGi
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Core Framework
>            Reporter: Thomas Diesler
>            Assignee: Thomas Diesler
>             Fix For:  JBossOSGi 1.0.0 Beta5
>
>
> The BundleStartStopDeployer always tries to resolve a bundle, which prevents test cases to only install a bundle

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira