Bug 849706

Created attachment 605731 [details]
server.log

"java.lang.ClassCastException: org.hibernate.ejb.EntityManagerFactoryImpl cannot be cast to org.hibernate.ejb.HibernateEntityManagerFactory" is thrown when using Hibernate 3 on EAP 6.0. Default Hibernate version in EAP 6.0 is 4, so to use Hibernate 3, then you have to disable it for your .war file manually by creating
app.war/WEB-INF/jboss-deployment-structure.xml. Setting up of my environment is described in this document:
https://docspace.corp.redhat.com/docs/DOC-111367

However Hibernate 4 detects persistence configuration of my .war files and throws the exception attached in server.log. I have tested human task with a simple test and the human task appears in business-central and it's possible to complete it, data passing in HT was not tested. So it's possible that Hibernate 4 has no effect on the deployed BRMS .war files that uses Hibernate 3, but it may bother server admins. To disable the error the only solution I have found is to disable whole JPA module and subsystem in standalone/configuration/standalone.xml of EAP 6.0, however that affects all other deployed applications which use Hibernate 4.

My environment:
EAP 6.0
BRMS 5.3.0 GA patch 01
PostgreSQL 9