Ejb jndi binding in java code - binding

Question

The method is loading a bean
Context ctx = new InitialContext();
Object lookupResult = ctx.lookup("abilitecConsumerClient/local");
And another class
#Stateless
#LocalBinding(jndiBinding="abilitecConsumerClient/local" )
#Local()
What exactly does represent abilitecConsumerClient/local? Is that the path in my local machine that I need to look for this property file or the file I need it loads for this EJB JNDI binding name?
If you can also give info how to specify a custom EJB JNDI binding name in JBoss EAP 6?
This app is going to run on JBOSS EAP 6.

Answer 1

According to the old JBoss documentation:
...when the application is deployed in a .jar, session beans will bind to JNDI in the form (...) ejbName/local in the case of local interfaces. When the EJBs are deployed in an .ear file, the default JNDI binding will be prepended by the name of the .ear file.
So, if we have an EAR file which name is foo.ear the default JNDI name would be foo/EJB-NAME/local.
This behavior can be overriden by defining our own #LocalBinding annotation on our bean.
By definition, the #LocalBinding annotation specifies the local JNDI binding for an EJB local interface.
Which means that the value of the element jndiBinding, passed on #LocalBinding, represents the name associated (binded) to the bean, where the annotation was placed, on the Java Naming and Directory Interface (JNDI).
This then allows us to retrieve an instance of the bean, as you mentioned, by looking it up on the JNDI, using the jndiBinding defined on the #LocalBinding annotation:
MyBean bean = ctx.lookup("abilitecConsumerClient/local");
NOW, regarding your last question, notice that in beginning of my answer I said ...old JBoss documentation.... Why? Because since JBoss EAP 6 (or JBoss AS 7), the binding of EJBs to custom JNDI names isn't allowed anymore either by annotations or XML configuration.
One may assume that it was due to the efforts of Java EE 6 to standardize EJB Namespaces.
You can take a closer look at the JNDI changes present on JBoss EAP 6, where EJB 3.1 introduced a standardized global JNDI namespace and a series of related namespaces that map to the various scopes of a Java EE application.
Making a parallel between prior EAP 6 and after, we have:
Prior to EAP 6
// Bean definition
#Stateless
#LocalBinding(jndiBinding="custom/MyBean")
public class MyBeanImpl implements MyBean {
(...)
}
// look-up
ctx = new InitialContext();
MyBean myBean = (MyBean) ctx.lookup("custom/MyBean");
After EAP 6
// Bean definition
#Stateless
#Local(MyBean.class)
public class MyBeanImpl implements MyBean {
(...)
}
// look-up
MyBean myBean = (MyBean)
InitialContext.lookup("java:module/MyBean");
// or through injection
#EJB
MyBean myBean;
Finally, you can find more examples on how to do the EJB look-up on the JBoss AS 7 examples and take a careful look at the following:
Portable JNDI sintax
Application-specified Portable JNDI Names
Section "Examples of JNDI mappings in previous releases and how they might look now" of How do I migrate my application from AS5 or AS6 to AS7