[jboss-dev-forums] [Design of OSGi Integration] - Re: JBOSGI-38 and bundle deployment order

[thomas.diesler@jboss.com]

I can confirm that deployment of A fails when the PackageAdminDependencyItem is added.


  | DEPLOYMENTS MISSING DEPENDENCIES:
  |   Deployment "vfszip:/.../jbosgi38-bundleA.jar/" is missing the following dependencies:
  |     Dependency "<UNKNOWN jbosgi38-bundleA>" (should be in state "ClassLoader", but is actually in state "** UNRESOLVED Bundle: jbosgi38-bundleA [5] **")
  | 

[09:17:02] Thomas Diesler: Let me summarise to verify that I understand this correctly ...
[09:18:06] … The MainDeployer does not "give up" on the deployment. The deployment context is still there. If a subsequent deployment satisfies the DI the deployment will still succeed ....
[09:18:51] Ales Justin: sure
[09:19:00] Thomas Diesler: The MainDeployer reports incomplete deployments with the WARN and actually throws an exception for incomplete deployments.

Ales suggests

[09:15:13] Ales Justin: 
[09:15:26] … perhaps we can do a new feature
[09:15:36] … ignored deployments
[09:16:04] … which don't show on the IncompleteDE

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

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