> That got me farther, but new error: > > 21:46:15,229 ERROR [AbstractKernelController] Error installing to Start: > name=persistence.unit:unitName=#CasPersistence state=Create > java.lang.ClassCastException: org.hibernate.ejb.HibernatePersistence cannot > be cast to javax.persistence.spi.PersistenceProvider
This is almost certainly a classloader problem since org.hibernate.ejb.HibernatePersistence clearly implements javax.persistence.spi.PersistenceProvider, http://docs.jboss.org/hibernate/stable/entitymanager/api/org/hibernate/ejb/HibernatePersistence.html. Recall that in Java a class must assignment compatible _and_ sourced from the same classloader in order for a cast to succeed; a ClassCastException will be thrown if both conditions are not met. > Is anyone out there using Jboss 5.0.1 with CAS 3.3.2 ? Thankfully, no. We run CAS 3.0.6 in production on JBoss 4.0.4, but we're moving to Tomcat 6 in the near future. JBoss is simply too complex for our needs with respect to CAS. Complicating that, JBoss 5.0 is new and dramatically different. I've looked at a lot of JBoss 4.x stack traces over the past few years, but what you cited is completely foreign to me. The new JBoss microkernel/microcontainer is just a totally new beast. 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
