About Question enthuware.oce-ejbd.v6.2.419 :

[Ciprian Mihalache]

Your explanation seems reasonable. Thank you

PS: I just discovered another question that has a similar option: enthuware.oce-ejbd.v6.2.420

[admin]

Updated here as well.

[himaiMinh]

Maybe, this is out of the scope of this question.
Session 21.3.2 JNDI Requirements: All EJB container must make available at least the following objects in the name space:
- The local business interface of other EJB ....
- EJBContext objects
- the resource factories used by the EJB ...

Does it mean without lookup or name attribute, we can inject a ConnectionFactory like this:

Code: Select all

@Resource
private ConnectionFactory connectionFactory;

?

We can inject EJBContext or UserTransaction or other EJB like this without any name/lookup attributes in @Resource:

Code: Select all

  @Resource
   EJBContext context;
 
  @UserTransaction
   UserTransaction ut;

  @EJB  //assume MyRemoteRef is the remote view of a bean in the same module;
   MyRemoteRef  myRemoteBean;

  @EJB  // assume MyLocalBean is the no-interface view of a bean in the same module;
   MyLocalBean myLocalBean;

[admin]

Yes, the container tries to inject appropriate object based on name and/or type.