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

[Jason T. Greene]

On 12/2/10 9:28 PM, David M. Lloyd wrote:
e to add one manifest entry.
>
> 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.

@EJB though specifies a unique bean via either a comp/module ref (which 
uses unique identifiers in the DD), OR via lookup and a JNDI path that 
points to one of the unique jndi paths of the ejb.

-- 
Jason T. Greene
JBoss, a division of Red Hat