This rule detects Enterprise JavaBeans(TM) (EJB) JNDI names from the jboss.xml files.
For each EJB 2.1 or earlier enterprise beans, you must specify a JNDI name. The name is used to bind an entry in the global JNDI name space for the EJB home object. For WebSphere traditional and Liberty, the binding definition is stored in the META-INF/ibm-ejb-jar-bnd.xmi file.
You do not need to manually assign JNDI bindings names for each of the interfaces or EJB homes on your enterprise beans in EJB 3.0 modules. If you do not explicitly assign bindings, the EJB container assigns default bindings.
An example JNDI name for a product EJB in a store application might be store/ejb/Product as shown in the following example.
Example jboss.xml <jndi-name>:The JNDI name value is migrated to the corresponding WebSphere Application Server bindings file. If the bindings file does not already exist, one is created.