In Runtime when we delegate most of the work to underlying OSGi framework,
we still need to tie into existing MC's lifecycle/dependency handling.
Otherwise the bundle will be pushed to Installed even though its cl isn't resolved.
We need to add a new DependencyItem
which does it's resolution based on Bundle resolution.
e.g. BudleDependencyItem
| public boolean resolve(Controller controller)
| {
| return bundle.isResolved(); // pseudo method
| }
|
Perhaps this also requires additional deployers
that will change the Bundle's state.
* one that would just install the bundle
* another one that would create it
* one that would start it (after bundle/cl was resolved)
(I need to check the spec on how exactly this goes :-))
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213159#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...