Hi Andy, Good to hear from you again. Hope you are doing well. I appreciate your quick response (but then again, you were always quick to response whenever I have had issues in the past).
Our product no longer uses AspectJ at all, so it's puzzling that we would be introducing a conflict. In fact, we now take precautions to ensure that we don't introduce these sorts of conflicts, by loading most of our classes on a separate, independent class loader. However, I suppose that this could cause an issue; a duplicately named class could still get loaded, and confuse the weaver. Unfortunately, it's hard to tell from the stack trace which class is being woven. I assume that Spring doesn't have any class loader 'hooks' like we do; I imagine that Spring uses the weaver to pre-processes application classes before presenting them to the class loader, so I can't see that the weaver would have any visibility to our classes. The customer in question is in Italy, so I won't find out the version number of Spring until tomorrow. I have also downloaded the 1.6 AspectJ jar files for them so we can try it tomorrow. Hopefully, it will work, and they will accept that as a workaround for the problem. If they want an explanation as to the root cause of the problem, I may have to take you up on your offer of providing a diagnostic jar file that prints the class name that is causing the problem. I will let you know more tomorrow. Thanks again for your help. Cheers, Bad -- View this message in context: http://aspectj.2085585.n4.nabble.com/AspectJ-NPE-in-Java15AnnotationFinder-tp2257835p2257956.html Sent from the AspectJ - users mailing list archive at Nabble.com. _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
