[jboss-jira] [JBoss JIRA] Commented: (JBAOP-356) Ability to attach a .aop deployment to a particular scoped classloader

[Kabir Khan (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAOP-356?page=comments#action_12353122 ] 
            
Kabir Khan commented on JBAOP-356:
----------------------------------

Done in Branch_AOP_1_5, and in Branch_4_0 via the created aop snapshot-Branch_AOP_1_5.
Need to get branch 4_2 working using aop snapshot-Branch_AOP_1_5, port over tests + changes to aspects/

These changes also need to go into aop trunk and as trunk

> Ability to attach a .aop deployment to a particular scoped classloader
> ----------------------------------------------------------------------
>
>                 Key: JBAOP-356
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-356
>             Project: JBoss AOP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.alpha2
>            Reporter: Kabir Khan
>         Assigned To: Kabir Khan
>             Fix For: 2.0.0.alpha3, 1.5.4.GA
>
>
> 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