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

[alesj]

"thomas.diesler at jboss.com" wrote : 
  | The MC Framework incorrectly uninstalls the bundle if there is a failure in bundle.start()
  | 
No, that is / should be the right behavior, as you don't wanna have broken service stuck in some middle state.

The is a notion of ErrorHandler in Controller, which might be useful,
if we decide to go down this path.

Imho, the real problem is how we handle this Bundle::start.

"thomas.diesler at jboss.com" wrote : 
  | 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.
  | 
Bundle::start should only be called after we're past CLASSLOADER stage.
At least in automated mode. If the user wants to do this before, it's his choice and potential fault.

"thomas.diesler at jboss.com" wrote : 
  | 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. 
  | 
Actually I solved it in some hackish way.
Afair, my problem was that I didn't know how to resolve cyclic bundles,
but that's actually Controller's resolve problem as it doesn't know how to resolve cyclic dependencies in the same state.

But yeah, I'm all for it that Adrian gets a stab at this problem. :-)
* Bundle:start issue
* cyclic bundle dependencies
* resolve algorithm performance issue (EmanuelM has a good example of this)


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

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