3.2. Changes Dependent on Your Application Architecture and Components

3.2.1. Review Changes Dependent on Your Application Architecture and Components

If your application uses any of the following technologies or components, you may need to make modifications to your application when you migrate to JBoss Enterprise Application Platform 6.
Hibernate and JPA
If your application uses Hibernate or JPA, your application may need some modifications. For more information, see: Section 3.2.2.1, “Update Applications That Use Hibernate and/or JPA”.
REST
If your application uses JAX-RS, you should be aware that JBoss Enterprise Application Platform 6 automatically sets up RESTEasy, so you no longer need to configure it yourself. For more information, see: Section 3.2.3.1, “Configure JAX-RS and RESTEasy Changes”
LDAP
The LDAP security realm is configured differently in JBoss Enterprise Application Platform 6. If your application uses LDAP, refer to the following topic for more information: Section 3.2.4.1, “Configure LDAP Security Realm Changes”.
Messaging
JBoss Messaging is no longer included in JBoss Enterprise Application Platform 6. If your application uses JBoss Messaging as the messaging provider, you need to replace the JBoss Messaging code with HornetQ. The following topic describes what you need to do: Section 3.2.5.2, “Migrate Your Application to Use HornetQ as the JMS Provider”.
Clustering
The way you enable clustering has changed in JBoss Enterprise Application Platform 6. For details, see: Section 3.2.6.1, “Make Changes to Your Application for Clustering”.
Service-style deployment
Although JBoss Enterprise Application Platform 6 no longer uses service-style descriptors, the container supports these service-style deployments without change where possible. For deployment information, see: Section 3.2.7.1, “Update Applications That Use Service-style Deployments”
Remote invocation
If your application makes remote invocations, you can still use JNDI to lookup a proxy for your bean and invoke on that returned proxy. For more information about required syntax and namespaces changes, see: Section 3.2.8.1, “Migrate JBoss Enterprise Application Platform 5 Deployed Applications That Make Remote Invocations to JBoss Enterprise Application Platform 6”.
Seam 2.2
If your application uses Seam 2.2, refer to the following topic for changes you need to make: Section 3.2.10.1, “Migrate Seam 2.2 Archives to JBoss Enterprise Application Platform 6”.
Spring
If your application uses Spring, see: Section 3.2.11.1, “Migrate Spring Applications”.
Other changes that may impact your migration
For additional changes in JBoss Enterprise Application Platform 6 that may impact your application, see: Section 3.2.12.1, “Become Familiar with Other Changes That May Affect Your Migration”.