[jboss-jira] [JBoss JIRA] Updated: (JBAOP-365) Compile-time woven class advisor initialization fails if mixins config is available at runtime

Galder Zamarreno (JIRA) jira-events at lists.jboss.org
Mon Feb 26 05:31:35 EST 2007


     [ http://jira.jboss.com/jira/browse/JBAOP-365?page=all ]

Galder Zamarreno updated JBAOP-365:
-----------------------------------

    Workaround Description: 
If you encounter this issue with 4.0.5.GA, until the update is available, do the following:

1. If you don't use http session clustering, you can remove tc5-cluster.aop from your 
deploy directory and use your own jboss-aop.xml. That should work.

2. If you do, you will need to include tc5-cluster.aop in your classpath when 
instrumenting the classes. Furthermore, you will need jboss-aop-aspect.jar 
(for aop aspects) in your classpath as well during compilation.
                Workaround: [Workaround Exists]

> Compile-time woven class advisor initialization fails if mixins config is available at runtime
> ----------------------------------------------------------------------------------------------
>
>                 Key: JBAOP-365
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-365
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.alpha2, 1.5.4.SP1, 1.5.4.GA, 1.5.3.GA, 1.5.2.GA
>            Reporter: Kabir Khan
>         Assigned To: Galder Zamarreno
>             Fix For: 2.0.0.alpha3, 1.5.4.SP2
>
>
> If a class is woven at compile-time and then at runtime a jboss-aop.xml containing mixins is available we fail when initialising the advisor. This is because the mixin interface methods are not present in the woven class. 
> Caused by: java.lang.RuntimeException: java.lang.NoSuchMethodException: addObserver
>      at org.jboss.aop.ClassAdvisor.attachClass(ClassAdvisor.java:312)
>      at org.jboss.aop.AspectManager.initialiseClassAdvisor(AspectManager.java:590)
>      at org.jboss.aop.AspectManager.getAdvisor(AspectManager.java:578)
>      at com.equitymethods.security.login.LoggedUser.<clinit>(LoggedUser.java)
>      ... 51 more
>  Caused by: java.lang.NoSuchMethodException: addObserver
>      at org.jboss.aop.ClassAdvisor.getMethod(ClassAdvisor.java:323)
>      at org.jboss.aop.ClassAdvisor.getMethod(ClassAdvisor.java:331)
>      at org.jboss.aop.ClassAdvisor.populateMixinMethods(ClassAdvisor.java:394)
>      at org.jboss.aop.ClassAdvisor$1.run(ClassAdvisor.java:290)
>      at java.security.AccessController.doPrivileged(Native Method)
>      at org.jboss.aop.ClassAdvisor.attachClass(ClassAdvisor.java:271)
>      ... 54 more 
> Need to check if the class actually implements the interface when populating the mixin methods

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

        



More information about the jboss-jira mailing list