Use WebSphere bindings to define EJB reference names

JBoss-specific deployment descriptors jboss-web.xml or the jboss.xml file might contain EJB references. These references map an EJB reference to its JNDI name. For the references to work correctly on WebSphere(R) Application Server, information must be moved to the WebSphere traditional or Liberty bindings file.

This rule flags EJB references found in jboss-web.xml file and jboss.xml file, if. After the automated fix is applied, it will mark the JBoss XML is marked with a comment indicating it has been migrated. This is used to determine whether to run the automated fix, and it can be used at the end of migration to indicate how much of the XML file has been migrated.

For example, if a JBoss web module references the EJB MyBean, the reference is defined in the jboss-web.xml file:

=jboss-web.xml constructs= =

<jboss-web>
<ejb-ref>
<ejb-ref-name>MyBean</ejb-ref-name>
<jndi-name>ejb/MyBean</jndi-name>
</ejb-ref>
</jboss-web>

The JNDI name is added to the Web module binding file. If the binding file does not exist, one is created.

Similarly, when an EJB reference is found in an EJB project, information is moved from the jboss.xml file to the ejb-jar.xml file and the EJB bindings file. For example, the following example shows MyBean2 referencing MyBean from the jboss.xml file.

jboss.xml constructs

<jboss>
<enterprise-beans>
<session>
<ejb-name>MyBean2</ejb-name>
<jndi-name>ejb/MyBean2</jndi-name>
<ejb-ref>
<ejb-ref-name>MyBean</ejb-ref-name>
<jndi-name>ejb/MyBean</jndi-name>
</ejb-ref>
</session>
</enterprise-beans>
</jboss>

Information about the reference is also added to the binding file. If the binding file does not exist, one is created.