3.2.12. JBoss AOP Changes

3.2.12.1. Update Applications That Use JBoss AOP

JBoss AOP (Aspect Oriented Programming) is no longer included in JBoss EAP 6. In previous releases, JBoss AOP was used by the EJB container. In JBoss EAP 6, the EJB container uses a new mechanism. If your application uses JBoss AOP, you must modify your application code as follows.
Refactor the Application

  • Standard EJB3 configurations that were previously made in the ejb3-interceptors-aop.xml file are now configured in the server configuration file. For a standalone server, this is the standalone/configuration/standalone-full.xml file. If you are running your server in a managed domain, this is the domain/configuration/domain.xml file.
  • Server side AOP Interceptors should be modified to use the standard Java EE Interceptor. For more information about container interceptors and how to use a client side interceptor in an application, refer to the chapter entitled Container Interceptors in the Development Guide for JBoss EAP 6 located on the Customer Portal at https://access.redhat.com/site/documentation/JBoss_Enterprise_Application_Platform/.

Use JBoss AOP Libraries

  • If you are not able to refactor the code, you can obtain a copy of the JBoss AOP libraries and bundle them with the application. The AOP libraries may work in JBoss EAP 6, but are not deployed. You can manually deploy them by using the following command line argument when you start your server: -Djboss.aop.path=PATH_TO_AOP_CONFIG

    Note

    Although the JBoss AOP libraries may work in JBoss EAP 6, this not a supported configuration.