JBoss.org Community Documentation
If you have an application using classloader isolation, as long as you have "prepared your classes" you can later attach a .aop file to that deployment. If
we have a .ear file scoped using a jboss-app.xml file, with the scoped loader repository jboss.test:service=scoped
:
<jboss-app> <loader-repository> jboss.test:service=scoped </loader-repository> </jboss-app>
We can later deploy a .aop file containing aspects and configuration to attach that deployment to the scoped .ear. This is done using the loader-repository
tag in the .aop files META-INF/jboss-aop.xml
file.
<?xml version="1.0" encoding="UTF-8"?> <aop> <loader-repository>jboss.test:service=scoped</loader-repository> <!-- Aspects and bindings --> </aop>
This has the same effect as deploying the .aop file as part of the .ear as we saw previously, but allows you to hot deploy aspects into your scoped application.