not blocking warning "may not be in your classpath"

[alexis_morelle]

Hi (again),

if you read my other post, I'm in the same application.
I use the standalone JBoss AOP api.

As I said, I don't have anything else then what I give you in the console. I have many (13) lines like these. I'm sorry if it's not easy to read.

[warn] Could not find class org.eclipse.core.resources.IWorkspaceRoot that org.eclipse.emf.ecore.resource.impl.URIConverterImpl references. It may not be in your classpath and you may not be getting field and constructor weaving for this class.
[warn] Could not find class org.eclipse.core.runtime.Platform that org.eclipse.emf.common.EMFPlugin references. It may not be in your classpath and you may not be getting field and constructor weaving for this class.
[warn] Could not find class org.eclipse.core.runtime.Platform that org.eclipse.emf.common.EMFPlugin references. It may not be in your classpath and you may not be getting field and constructor weaving for this class.
[warn] Could not find class org.eclipse.core.runtime.IProgressMonitor that org.eclipse.xsd.util.XSDResourceImpl references. It may not be in your classpath and you may not be getting field and constructor weaving for this class.
[warn] Could not find class org.eclipse.core.runtime.Platform that org.eclipse.emf.common.EMFPlugin references. It may not be in your classpath and you may not be getting field and constructor weaving for this class.
[warn] Could not find class org.apache.xerces.impl.Version that nu.xom.Builder references. It may not be in your classpath and you may not be getting field and constructor weaving for this class.

As I have no aspect referencing any of these classes, my question is the same, I'd like to know where it could come from.

Thank you by advance,
Alexis.

[stalep]

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.

[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.

[flavia.rainone]

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