I have built a web application using spring-mvc and mongodb as database. I used maven3 to build the application.
Project builds successfully but when application sta
Update for those moving to versions above 3.1.x ... as made clear by this answer here there is no longer a separate spring-asm
, so it would be better to exclude spring-asm
altogether, once you're at Spring version 3.2.x
This error usually shows up when incomptiable versions of jars are used, for example spring-asm
and spring-core
. Have a look at forum.springsource.org/showthread.php?133341
In spring version > 3.2.0, you no longer need to explicitly include spring-asm
since it has already been included in spring-core
.
Remove spring-asm
from your build definition and ensure that spring-core
is there.
http://static.springsource.org/spring-framework/docs/current/spring-framework-reference/html/migration-3.2.html#migration-3.2-inline-asm
This error happens when the loaded class i.e. ClassMetadataReadingVisitor
does not respect the contract of inherited abstract class or interface i.e. ClassVisitor
.
Looks like at load time different versions of the above classes are getting loaded in your case.
Seems you have new spring-core jar and old spring-asm jar in your application. ClassMetadataReadingVisitor
class is getting loaded from spring-core and ClassVisitor
from spring-asm.
Please check using maven dependency:tree
command to see the dependent jars.
I had the same problem and faced it by deleting my spring-data-jpa
dependency from pom.xml
It's already included in the spring-core
dependency.