Hi Anthony, Do you mean the optimized matching that became default in AspectJ 1.6.7 onwards? (Discussed here: http://andrewclement.blogspot.com/2009/11/aspectj-how-much-faster-is-aspectj-167.html ). Ideally I'd like to fix any bugs so it isn't causing you an issue under Spring - do you want to raise an AspectJ bug for the problem? There is a configuration option for the weaver that turns it off:
-Xset:optimizedMatching=false But I'm not sure where you would set that, it depends on your spring configuration. I would normally set it either on the command line (if compile time weaving), or in an aop.xml file (if loadtime weaving). cheers Andy On 4 January 2011 18:40, Anthony Tang <aan...@yahoo.com> wrote: > Hi - > > I am having a problem with optimized matching specific to a custom Adaptor > Factor Bean I have in Spring. While trying to figure that out, it looks > like I can get around it by turning off "optimized matching", but I can't > find documentation on how to specify these configurations. > > How do I specify an option to the JVM so that aspectj turns off optimized > matching? I am running a web application deployed as an EAR in JBoss. > > Thanks! > > _______________________________________________ > aspectj-users mailing list > aspectj-users@eclipse.org > https://dev.eclipse.org/mailman/listinfo/aspectj-users > > _______________________________________________ aspectj-users mailing list aspectj-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users