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

thomas.diesler@jboss.com do-not-reply at jboss.com
Fri Nov 20 05:05:18 EST 2009


anonymous wrote : 
  | The OSGi spec takes a different (and probably incorrect :-) view. 
  | 

I disagree. A bundle that is INSTALLED has no classloader nor bundle context associated with it. You can use PackageAdmin for an attempt to resolve that bundle. If that fails, the bundle is still INSTALLED. If that succeeds the bundle is RESOLVED, you can then use bundle.start() to start the bundle (i.e. call BundleActivator). If that fails the bundle is still RESOLVED. In no case does the bundle get uninstalled if a transition to the RESOLVED or ACTIVE state fails.

anonymous wrote : 
  | So the solution is to add an ErrorHandler to the DeploymentControllerContext if it is an OSGi deployment,
  | 

Ok, here is the issue

https://jira.jboss.org/jira/browse/JBDEPLOY-225

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

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



More information about the jboss-dev-forums mailing list