[jboss-dev-forums] [Design of OSGi Integration] - Re: Runtime and bundle lifecycle/dependency resolution

[alesj]

"thomas.diesler at jboss.com" wrote : 
  | I'd suggest the BundleStartStopDeployer maintains a list of unresolved bundles and tries to resolve them before bundle.start() is attempted.
  | 
MC already does this.
Bundle == DeploymentControllerContext.

You're missing my point.
We should make sure the Bundle only gets to BSSD if it's properly resolved.
Any other hacking/duplicating is a step in the wrong direction.

"thomas.diesler at jboss.com" wrote : 
  | We could make PackageAdmin a required service without which BundleStartStopDeployer cannot start bundles automatically. 
  | 
I wouldn't be that strict.
Having PackageAdmin means having few more jars/bundles.
If it's there, great, if not fallback to (2) or in the worst case (3).

"thomas.diesler at jboss.com" wrote : 
  | Only if this approach fails I'd investigate (2) or (3)
Fine by me.
As long as you make it behind under nice spi/api.

e.g. BundleClassLoaderDependencyDeployer::createResolveDependencyItem() could return diff DI instance based on what is available


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

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