3.2.11. EJB 2.x Changes
3.2.11.1. Update Applications That Use EJB 2.x
JBoss EAP 6 provides support for EJB 2.x, however, you need to make a few code modifications and start the server with the full profile.
Procedure 3.26. Run EJB 2.x on JBoss EAP 6
Modify the Code to Use the New JNDI Namespace Rules
As with EJB 3.0, you must use the full JNDI prefix with EJB 2.x. For more information on the new JNDI namespace rules and code examples, see Section 3.1.8.1, “Update Application JNDI Namespace Names”.Examples showing how to update JNDI namespaces from previous releases can be found here: Section 3.1.8.5, “Examples of JNDI Namespaces in Previous Releases and How They are Specified in JBoss EAP 6”.Modify the
jboss-web.xml
File DescriptorModify the<jndi-name>
for each<ejb-ref>
to use the new JNDI fully qualified lookup format.Replace the
jboss.xml
deployment descriptor fileThejboss-ejb3.xml
deployment descriptor replaces thejboss.xml
deployment descriptor to override and add to the features provided by the Java Enterprise Edition (EE) definedejb-jar.xml
deployment descriptor. The new file is incompatible withjboss.xml
, and thejboss.xml
is now ignored in deployments.Start the Server with the Full Profiles
EJB 2.x requires the Java Enterprise Edition 6 Full Profile. To start JBoss EAP 6 with the full profile, pass the argument-c standalone-full.xml
on the command line when you start the server.Clustering is no longer supported
Clustering of EJB 2.x entity beans is no longer supported in JBoss EAP 6.