3.2.12. JBoss AOP Changes
18.104.22.168. Update Applications That Use JBoss AOP
- Standard EJB3 configurations that were previously made in the
ejb3-interceptors-aop.xmlfile are now configured in the server configuration file. For a standalone server, this is the
standalone/configuration/standalone-full.xmlfile. If you are running your server in a managed domain, this is the
- 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/.
- 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:
NoteAlthough the JBoss AOP libraries may work in JBoss EAP 6, this not a supported configuration.