[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5304?page=c...
]
Galder Zamarreno commented on HHH-5304:
---------------------------------------
So, if anyone ever wanted to get Infinispan 2LC to work on AS 5.1, it would be easier to
attempt to port Infinispan 2LC to Hibernate 3.4 instead? I don't remember any major
changes in terms of caching since 3.3.
Deploying Hibernate 3.5 in isolated classloader in AS 5.1 fails
---------------------------------------------------------------
Key: HHH-5304
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5304
Project: Hibernate Core
Issue Type: Bug
Affects Versions: 3.5.2
Reporter: Galder Zamarreno
Assignee: Steve Ebersole
Deploying Hibernate 3.5 within an isolated deployment in AS 5.1, where Hibernate 3.3 or
3.4 runs, fails with:
3:29:34,255 INFO [PersistenceUnitDeployment] Starting persistence unit
persistence.unit:unitName=InfiniSeam-ear.ear/InfiniSeam-ejb.jar#InfiniSeam
13:29:34,305 ERROR [AbstractKernelController] Error installing to Start:
name=persistence.unit:unitName=InfiniSeam-ear.ear/InfiniSeam-ejb.jar#InfiniSeam
state=Create
java.lang.ClassCastException: org.hibernate.ejb.HibernatePersistence cannot be cast to
javax.persistence.spi.PersistenceProvider
Taking in account that org.hibernate.ejb.HibernatePersistence extends
javax.persistence.spi.PersistenceProvider, this would appear to be an issue of the first
class being loaded with a CL and the second one with a different one.
Since org.hibernate.ejb.HibernatePersistence is something that's defined in the
persistence.xml, there might be a change that this class is loaded from the wrong place
rather than the .ear file (This is just a hunch though):
<provider>org.hibernate.ejb.HibernatePersistence</provider>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira