Adrian, in case you are wondering what would be cause of the bug... The method Advisor.hasAnnotation(), that has the annotation name and the annotation class, was calling Advisor.hasJoinpointAnnotationFromStringName() method. This method receives only the annotation name and tries to load its class... so, a simple refactoring avoided this unnecessary class loading step, which was the one that was generating the error. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115572#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...