> here is the error message > ]] Root cause of ServletException. > java.lang.NoSuchMethodError: > javax.persistence.Persistence.getPersistenceUtil()Ljavax/persistence/PersistenceUtil; > at
We've seen this before. The cause is likely your container providing a JPA 1.0 provider, while CAS requires a JPA 2.0 API/provider. While CAS ships with the the correct libraries, Weblogic is likely defaulting to the container-provided libraries, and CAS is having problems when the Hibernate validation engine, which also relies on the JPA API, performs JSR 303 validation. So this has absolutely nothing to do with JPA and database persistence; it's merely an artifact of our validation engine (hibernate-validator) requiring a specific JPA version. Most containers have a "classloader isolation" (what it's called in JBoss) feature where you can configure a deployed application not to delegate to the container classloader for some/all libraries. I can't help with Weblogic configuration in that regard, but I believe it's possible. I'm fairly certain other CAS deployers have successfully configured Weblogic for this in the past, so searching cas-user archives may be of help. Please let us know in any case whether you resolve this issue. Best wishes, M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
