hm, its quite possible that we have several concurrent issues with the generated advisors instrumentation that uses SuperClassesFirstWeavingStrategy. you can easily tell jboss aop to use a different instrumentor (its only from jboss aop 2.0 that generated advisors are default instrumentor). add this property to either aopc or as a systemproperty when you run the program:
| jboss.aop.instrumentor = org.jboss.aop.instrument.ClassicInstrumentor | then you will get the "old" instrumentor, please let us know if you still have the problem with this instrumentor. to get more verbose output (and which instrumenter thats used) set this property to true: "jboss.aop.verbose" - and yes, jboss aop will load all classes into its instrumentor to check if the class match any of the pointcuts/aspects/etc. if it doesnt match anything it doesnt do anything, but it will check all classes. thanks for the info and good work btw, these kinds of bugs isnt very easy to reproduce in a test so real world apps and feedback are very appreciated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990947#3990947 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990947 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
