10

I get the error using an aspect in our application.

What do I need to fix this error or what does this say to me?

[AppClassLoader@13b8f62] error can't determine superclass of missing type xxx.yyy.zzz.execution.SystemVersion
when weaving type xxx.yyy.zzz.execution.DefaultDServerConfigurator
when weaving classes 
when weaving 
 [Xlint:cantFindType]
gvlasov
  • 18,638
  • 21
  • 74
  • 110
Tima
  • 12,765
  • 23
  • 82
  • 125

3 Answers3

9

Changing the option cantFindType to

{cantFindType = warning}

in the ajc.properties file solved the problem to me.

You can specify the property file with -Xlintfile d:\temp\ajc.properties

gvlasov
  • 18,638
  • 21
  • 74
  • 110
user2424279
  • 91
  • 1
  • 2
6

Had the same issue with oracle and kamon-jdbc, adding the following resources/META-INF/aop.xml file helped:

 <!DOCTYPE aspectj PUBLIC "-//AspectJ//DTD//EN" "http://www.eclipse.org/aspectj/dtd/aspectj.dtd">

 <aspectj>
     <weaver options="-Xlint:ignore">
         <include within="oracle.jdbc..*"/>
     </weaver>
 </aspectj>
ptrlaszlo
  • 337
  • 4
  • 9
5

This means that when weaving type xxx.yyy.zzz.execution.DefaultDServerConfigurator, the type xxx.yyy.zzz.execution.SystemVersion is required, but either SystemVersion or its superclass cannot be loaded because dependencies are missing.

Essentially, the aspects require extra class files/jars that are not on your classpath at runtime.

Andrew Eisenberg
  • 28,387
  • 9
  • 92
  • 148
  • Thanks. Actually it's strange behaviour between maven and Eclipse. But your answer help me to find out the problem. – Tima May 15 '12 at 13:35
  • Yeah, I thought it would have been something like that. :) – Andrew Eisenberg May 15 '12 at 16:01
  • @Mur Votema, how did you solve your problem with Maven+Eclipse? I'm seeing the same errors (although using TomcatInstrumentableClassLoader) – herman Dec 20 '12 at 17:02