[
http://jira.jboss.com/jira/browse/JBAOP-366?page=all ]
Kabir Khan updated JBAOP-366:
-----------------------------
Fix Version/s: 2.0.0.alpha6
(was: 2.0.0.alpha5)
Ability to attach a .aop deployment to a particular scoped
classloader
----------------------------------------------------------------------
Key: JBAOP-366
URL:
http://jira.jboss.com/jira/browse/JBAOP-366
Project: JBoss AOP
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.alpha3
Reporter: Kabir Khan
Assigned To: Kabir Khan
Fix For: 2.0.0.alpha6
e.g. if an .ear file has been scoped with:
<jboss-app>
<loader-repository>
dot.com:loader=ear1test
</loader-repository>
</jboss-app>
It should be possible to deploy at a later time a .aop file like:
<aop>
<attach-scoped-loader>dot.com:loader=ear1test</attach-scoped-loader>
<!-- aspects, bindings etc. -->
</aop>
The classloader for the scoped repository "dot.com:loader=ear1test" should be
used to deploy the contents of the .aop file in the same way as if the .aop file had been
deployed as part of the .ear.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira