"beve" wrote : | The dependencies are added by the EsbConfigParser deployer by extracting the dependency information from deployment.xml. | Your dependency kicks in too late, hence the CNFE. And you are just describing a module (transitively for class/package) dependency for a single bean (EsbDeployment) which might not be enough. You can still use your mechanism, but then the demand must have whenRequired before or equal PreInstall. "beve" wrote : | If one deployment has a dependency on another does that imply that the one defining the dependency has access to the other deployments classes? | If there is no explicit ClassLoadingMetaData (e.g. jboss-classloading.xml), then you have the same behavior as 4.x - flat "big ball of mud". ;-) If CLMD is present, then we follow "OSGI-ish" rules. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226102#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...