Hi I am using AspectJ 1.6.2 with Spring 3.0 support for LTW. This is a follow up to an issue I posted a while back on this list and did not follow up. I use AspectJ LTW in concert with Spring 3.0 in my application. I have a few aspects that are woven by AspectJ runtime and few others where I would like to use Spring's proxy style aspects.
In certain cases, I find that AspectJ runtime weaves aspects (declared with @Aspect annotation) that have not been declared in the aop.xml, consequently Spring refuses to apply these aspects using its proxy mechanism since it detects that AspectJ runtime has already woven it(by looking at the fields starting with 'ajc$' names). I have tried replicating this in a standalone application so as to submit a bug report, but I am unable to replicate the issue in this standalone app.I wonder if this is an issue in my application itself. What I would like is some pointers in terms of understanding how AspectJ runtime scans the aspects to weave and what gets woven.I was hoping some one could point me to the classes where this scanning (and the decisions to weave/not-weave happen) so that I can debug and see whats happening at load time and check why my undeclared aspects gets woven at all. Thanks -Satish _______________________________________________ aspectj-users mailing list aspectj-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users
