Re: [jboss-as7-dev] Deployment Chain/Service interaction

If implicitly detecting EJB interdependencies based on annotations becomes a requirement, I see other downsides as well. For example this would mean that at a container level, there can only be one EJB with a given interface name (otherwise there'd be no way to "wire" reliably), which means that deploying multiple EJB JARs defining an EJB with the same class or interface name is impossible for no good reason. EJBs are normally identified by app name/module name/bean name - or in the case of top level EJB JARs, just module name/bean name - and by having detection based upon a global EJB name scope we defeat this.