[jboss-dev-forums] [JBoss OSGi Development] - No explicit control over bundle.start()

thomas.diesler@jboss.com do-not-reply at jboss.com
Thu Nov 12 21:54:08 EST 2009


https://jira.jboss.org/jira/browse/JBOSGI-99

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 

Adrian, this seems to be a fundamental problem for which neither Ales nor I could come up with a solution. Could you perhaps have a look at this issue.

It is also related to PROPERTY_AUTO_START and the DeployerWrapper

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4265383#4265383

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4265383



More information about the jboss-dev-forums mailing list