Edit Question - KnowledgeHub

Title Body

I'm trying to upgrade to Hibernate 3.5.3-FINAL. When running my unit tests, I now receive the following exception: java.lang.NoSuchMethodError: javax.persistence.OneToMany.orphanRemoval()Z at org.hibernate.cfg.AnnotationBinder.processElementAnnotations(AnnotationBinder.java:1837) My classpath contains the following JAR's: From the hibernate dist: antlr-2.7.6.jar commons-collections-3.1.jar dom4j-1.6.1.jar javassist-3.9.0.GA.jar jta-1.1.jar slf4j-api-1.5.8.jar cglib-2.2.jar hibernate-jpa-2.0-api-1.0.0.Final.jar hibernate3.jar Other jars: blazeds-common-3.2.0.3978.jar blazeds-core-3.2.0.3978.jar blazeds-opt-3.2.0.3978.jar blazeds-proxy-3.2.0.3978.jar blazeds-remoting-3.2.0.3978.jar commons-lang-2.3.jar dbunit-2.4.7.jar ejb3-persistence.jar // Note, I've tried excluding this, but I get different errors guava-r05.jar hsqldb-1.8.0.7.jar junit-4.1.jar lambdaj-2.0-with-dependencies.jar log4j-1.2.14.jar mockito-all-1.8.0.jar persistence-api-1.0.jar spring-security-core-2.0.0.jar spring.jar sqljdbc.jar I've researched this, and I find answers that state my webserver must be JPA2 Compliant: Unfortunately if your app server is not JPA 2 compliant, you are likely to be out of luck This project is a library, not a webserver project. (Although it is eventually deployed to a webserver, I'm simply running unit tests here) What am I missing? <indulgent_rant> As a sidenote, it's very frustrating that every time I upgrade Hibernate, I find myself spending hours researching conflicting jars for MethodNotFoundException or ClassNotFoundException 's. There must be a simpler way? I thought for sure that with the announcement they were mer

Tags (comma-separated) Cancel