[
https://jira.jboss.org/jira/browse/JBAOP-695?page=com.atlassian.jira.plug...
]
Flavia Rainone updated JBAOP-695:
---------------------------------
Fix Version/s: 2.2.0.GA
Before fixing this one, we will wait for 2.1.0GA release, when the classloader leaks will
be fixed.
Hot un/deployment of .aop file works with war only when
UseJBossWebLoader is enabled
------------------------------------------------------------------------------------
Key: JBAOP-695
URL:
https://jira.jboss.org/jira/browse/JBAOP-695
Project: JBoss AOP
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.SP1
Reporter: Flavia Rainone
Assignee: Flavia Rainone
Fix For: 2.2.0.GA
To reproduce the bug, follow in the steps:
-Package your web application in a WAR just like normal.
-Package your jboss-aop.xml and interceptor(s) in an AOP archive (e.g.
myInterceptors.aop).
-Start JBoss with both the WAR and the AOP archive in the "deploy" directory
and load-time weaving enabled. When JBoss starts it will examine the point-cuts in the
jboss-aop.xml of your AOP archive and weave the classes in your WAR accordingly.
-To enable your interceptor(s), leave your AOP archive in the "deploy"
directory.
-To disable your interceptor(s), remove your AOP archive from the "deploy"
directory.
You will notice that the hot deploy is not working. It will work only if you change
"UseJBossWebLoader" to "true" in
<JBOSS_HOME>/server/default/deploy/jboss-web.deployer/META-INF/jboss-service.xml.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira