[jboss-jira] [JBoss JIRA] Commented: (JBAOP-658) Index InterceptionMarkers by classloader

[Kabir Khan (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAOP-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12432234#action_12432234 ] 

Kabir Khan commented on JBAOP-658:
----------------------------------

Having InterceptionMarkers indexed by classloader resolves this problem

> Index InterceptionMarkers by classloader
> ----------------------------------------
>
>                 Key: JBAOP-658
>                 URL: https://jira.jboss.org/jira/browse/JBAOP-658
>             Project: JBoss AOP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Kabir Khan
>            Assignee: Kabir Khan
>             Fix For: 2.0.0.GA
>
>
> skipField/ConstructorInterception are set for AnnnotatedSecuredPOJO when running AOPUnitTestCase without base-aspects.xml deployed following from JBAOP-647 (AOPUnitTestCase also deploys the classes for SecurityUnitTestCase). This only gets cleared when weaving the class in question, and is used when converting references for a class being woven. When running SecurityUnitTestCase, which deploys base-aspects.xml, AnnotatedSecuredPOJO is woven after SecurityTester, so the skipField/ConstructorInterception flags are still returning true for AnnotatedSecuredPOJO when converting SecurityTester's references. This means that the calls to AnnotatedSecuredPOJO's fields and constructors in SecurityTester are not replaced by calls to the wrapper methods.
> JBAOP-647 is not the cause of this behaviour, but it made this show up in the AS testsuite.

-- 
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