Home › OC4J: Exception creating EntityManagerFactory using PersistenceProvider class org.hibernate.ejb.HibernatePersistence for persistence unit DefaultPU

OC4J: Exception creating EntityManagerFactory using PersistenceProvider class org.hibernate.ejb.HibernatePersistence for persistence unit DefaultPU 

Dr. Xi
Joined:
04/09/2007
Posts:
710

March 02, 2010 00:07:48    Last update: March 02, 2010 00:07:48
OC4J didn't offer much help in the console. This is all it displayed: 
2010-03-01 15:48:21.372 ERROR J2EE EJB-03027 [FabulousApp] An error occured 
deploying EJB module: com.evermind.server.ejb.exception.DeploymentException: 
[FabulousApp:TheEJBModule] - Exception creating EntityManagerFactory using 
PersistenceProvider class org.hibernate.ejb.HibernatePersistence for persistence
unit DefaultPU.
10/03/01 15:48:21 WARNING: Application.setConfig Application: FabulousApp is 
in failed state as initialization failed. java.lang.InstantiationException: Error 
initializing ejb-modules: [FabulousApp:TheEJBModule] - Exception creating EntityManagerFactory 
using PersistenceProvider class org.hibernate.ejb.HibernatePersistence for 
persistence unit DefaultPU.
2010-03-01 15:48:21.403 WARNING J2EE OJR-00013 Exception initializing deployed 
application: FabulousApp. Application: FabulousApp is in failed state as 
initialization failed


However, in the em console, Logs -> Diagnostic Logs gives more details:

Message Text 
[FabulousApp] An error occured deploying EJB module: com.evermind.server.ejb.exception.DeploymentException: [FabulousApp:TheEJBModule]
  - Exception creating EntityManagerFactory using PersistenceProvider class org.hibernate.ejb.HibernatePersistence for persistence unit
  DefaultPU.


Supplemental Text 
com.evermind.server.ejb.exception.DeploymentException: [FabulousApp:TheEJBModule] - Exception creating EntityManagerFactory
  using PersistenceProvider class org.hibernate.ejb.HibernatePersistence for persistence unit DefaultPU.
        at com.evermind.server.ejb.exception.DeploymentException.exceptionCreatingEntityManagerFactory(DeploymentException.java:130)
        at com.evermind.server.ejb.persistence.PersistenceUnitManagerImpl.createContainerEntityManagerFactory(PersistenceUnitManagerImpl.java:197)
        at com.evermind.server.ejb.persistence.PersistenceUnitManagerImpl.initializePersistenceUnit(PersistenceUnitManagerImpl.java:159)
        at com.evermind.server.ejb.persistence.PersistenceUnitManagerImpl.initialize(PersistenceUnitManagerImpl.java:87)
        at com.evermind.server.ejb.EJBPackageDeployment.initializePersistenceUnitManager(EJBPackageDeployment.java:1074)
        at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:841)
        at com.evermind.server.ApplicationStateRunning.initializeApplication(ApplicationStateRunning.java:235)
        at com.evermind.server.Application.setConfig(Application.java:460)
        at com.evermind.server.Application.setConfig(Application.java:361)
        at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1919)
        at com.evermind.server.ApplicationServer.initializeDeployedApplications(ApplicationServer.java:1667)
        at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1050)
        at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:131)
        at java.lang.Thread.run(Thread.java:595)
    Caused by: org.hibernate.AnnotationException: mappedBy reference an unknown target entity property: fabulous.entities.Schedule.incrementTypeId
  in fabulous.entities.IncrementTypes.scheduleCollection


The error was caused by a relationship annotation between two entities, the referenced attribute was removed from the owner side: 
@OneToMany(cascade=CascadeType.ALL, mappedBy="incrementTypeId")
    private Collection<Schedule> scheduleCollection;

Share |
| Comment  | Tags
 
Easy email testing with http://www.ximailstop.com