Discussion :

[Frostizz]

J'ai un ejb stateless qui s'appel UserFacadeBean et son interface UserFacade. Dans mon client (application web) pour le récupérer j'utilise:
ctx.lookup("hello/UserFacadeBean/local"); oû hello et le nom de mon .ear.
Sous jboss ca marche niquel. Mais sous glassfish, il ne me trouve pas cet EJB pourtant il est bien déployer: not found ou not bound.

L'utilisation "<nom-ear>/<nom-ejb>/local" ou /remote, n'est-elle pas standard ?

[XmasRock]

Et non, ce n'est pas standard. Dans la Doc de JBoss EJB3:

Chapter 1. @EJB and <ejb-ref>

Rules for the @EJB annotation

* The @EJB annotation also has a mappedName() attribute. The specification leaves this a vendor specific metadata, but JBoss recognizes mappedName() as the global JNDI name of the EJB you are referencing. If you have specified a mappedName(), then all other attributes are ignored and this global JNDI name is used for binding.
* If you specify @EJB with no attributes defined:

@EJB ProcessPayment myEjbref;

Then the following rules apply:
o The EJB jar of the referencing bean is contained in is search for another EJB with the same interface. If there are more than one EJB that publishes same business interface, throw an exception, if there is one, use that one.
o Search the EAR for EJBs that publish that interface. If there are duplicates, throw an exception, otherwise return that one.
o Search globally in JBoss for an EJB of that interface. Again, if duplicates, throw an exception
* @EJB.beanName() corresponds to <ejb-link>. If the beanName() is defined, then use the same algorithm as @EJB with no attributes defined except use the beanName() as a key in the search. An exception to this rule is if you use the ejb-link '#' syntax. The '#' syntax allows you to put a relative path to a jar in the EAR where the EJB you are referencing lives. See spec for more details

For XML the same rules apply as annotations exception <mapped-name> is the ejb-jar.xml equivalent to @EJB.mappedName().