How to Fix Nosuchmethodexception With Classvalidator Exception
Note I'm using jboss-5.1.0.GA If you ever encounter the following error: Caused by: org.hibernate.AnnotationException: java.lang.NoSu...
https://www.czetsuyatech.com/2011/02/java-troubleshooting-classvalidator-exception-fix.html
Note I'm using jboss-5.1.0.GA
If you ever encounter the following error:
Caused by: org.hibernate.AnnotationException: java.lang.NoSuchMethodException: org.hibernate.validator.ClassValidator.(java .lang.Class, java.util.ResourceBundle, org.hibernate.validator.MessageInterpolator, java.util.Map, org.hibernate.annotations.common.reflection.Reflec tionManager)
It's probably caused by hibernate jars somewhere in your classpath or most probably:
JBOSS5_INSTALL_DIR/common/lib/hibernate*.jar
Just removed them, if you intended to use the jar files in your package.
hibernate-core
hibernate-annotations
hibernate-commons-annotations
hibernate-entitymanager
hibernate-validator
hibernate-jmx
If you ever encounter the following error:
Caused by: org.hibernate.AnnotationException: java.lang.NoSuchMethodException: org.hibernate.validator.ClassValidator.
It's probably caused by hibernate jars somewhere in your classpath or most probably:
JBOSS5_INSTALL_DIR/common/lib/hibernate*.jar
Just removed them, if you intended to use the jar files in your package.
hibernate-core
hibernate-annotations
hibernate-commons-annotations
hibernate-entitymanager
hibernate-validator
hibernate-jmx
2 comments
Remove them and you've removed about half the JBoss implementation of the EBJ3 spec. The main reason for using a JEE container is to take advantage of the facilities it provides. If you want to package all of this stuff in your application, you're better off deploying in something like tomcat.
Yes, I understand that. Unfortunately I'm working on a project that already have those jar files, that's why I have no choice but to remove the jars that came from the web server.
Post a Comment