We currently have an application that we have been running in Glassfish that we are migrating to use in Weblogic 12c. Leaving the existing project in place, I have moved all the code, resources, etc. to a new project where I've need to make some modifications related to the use of Weblogic and some of the weblogic provided extensions for JMS. One of the problems that I am experiencing is an issue related to the use of JPA.

Below is the error message I'm getting when attempting to access the admin page for the application:

<Jan 24, 2013 8:09:17 AM CST> <Warning> <HTTP> <BEA-101372> <There was a failure in application ServletContext@297087696[app:_auto_generated_ear_ module:WeblogicTaskServer path:null spec-version:3.0] when attempting to inject dependencies into tnt.wl.webapp.TaskStatusServlet. Dependencies will not be injected into this class.java.lang.IllegalArgumentException: No persistence unit named 'emf' is available in scope WeblogicTaskServer. Available persistence units: [] at weblogic.persistence.ModulePersistenceUnitRegistry.getPersistenceUnit(ModulePersistenceUnitRegistry.java:130)
at weblogic.persistence.PersistenceManagerFactoryObjectFactory.getPersistenceContextFactory(PersistenceManagerFactoryObjectFactory.java:73)
at weblogic.persistence.PersistenceManagerFactoryObjectFactory.getObjectInstance(PersistenceManagerFactoryObjectFactory.java:40)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:251)
Truncated. see log file for complete stacktrace
>

Does anyone know if this is an issue in the project itself or does this seem to be a config or registration problem within Weblogic? Have very little experience with the use of JPA and persistence.