anonymous wrote : Or am I going about this the wrong way? Should I be packaging hibernate differently in my ear? Put it in a .sar or .har?
What you have done so far (using the classloader scoping) is the correct way. anonymous wrote : | Caused by: 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.ReflectionManager) The exception that you are getting, does indicate that the classloader scoping is working and "your" hibernate jars have been picked up. If they weren't picked up, then you wouldn't have seen any exceptions since JBoss already has all the required correct versions of the jars. All we have to do now is figure out that your application has packaged all the "required" hibernate jars and the correct version of each of them. Let me try and find the thread where we had a similar discussion about upgrading hibernate in JBoss. By the way, i believe your WAR does not have any hibernate related jars. All those hibernate jars are in the lib of the EAR right? And what version is the hibernate-commons-annotations.jar? (You can open the MANIFEST.MF in that jar and see the version details). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170795#4170795 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170795 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
