-
1. Re: not blocking warning
stalep Feb 26, 2009 5:12 AM (in response to alexis_morelle)hi, if youre not intercepting any of the classes it says it cant find, then you can safely ignore those messages.
during processing of the classes aop will try to lookup all the classes and its references. often the references cant be found in the classpath and hence these warnings will occur.
its possible to set aop in a more stricter mode withe the option -suppress, if you set it to false aop will throw an exception when there are references to classes it cant find. -
2. Re: not blocking warning
alexis_morelle Feb 26, 2009 10:27 AM (in response to alexis_morelle)Thanks for your answer, I'm glad it's safe but I'm still wondering why I've got these messages.
The project is a bit large so I can't check it all but the developers insure me that the noticed classes are not used and that's why they are not in the classpath. The jboss-aop.xml file is short and simple and nor references these.
Where does these references come from...? I dunno. (^_^)
Thanks again,
Alexis. -
3. Re: not blocking warning
flavia.rainone Mar 30, 2009 4:34 PM (in response to alexis_morelle)Alexis,
These references come from code that JBoss AOP is parsing in order to peform weaving.
Whenever JBoss AOP finds a class in the source classpath (the one that you set, telling JBoss AOP where to find the classes that must be weaved), JBoss AOP needs to check on every reference to another class, to see if that reference (it could be a call, the type of a field, etc) is a joinpoint that must be weaved. When JBoss AOP doesn't find that referenced class in the classpath, it will print a message warning you of this.
So, there are classes in the source classpath that reference the classes mentioned in the warning messages.
Regards