Can TopLink Be Used For JPA Provider In 10.1.3.x Release?
(Doc ID 949525.1)
Last updated on APRIL 06, 2015
Applies to:Oracle TopLink - Version 10.1.3.1 to 10.1.3.5 [Release AS10gR3]
Information in this document applies to any platform.
***Checked for relevance on 15-Feb-2012***
You have downloaded Oracle Toplink 10.1.3.x and followed the installation instructions:
'Installing Oracle TopLink with Oracle Containers for J2EE' as found here:
When you deploy an EJB 3.0 application and invoke a JPA Entity, you see in the server log:
However, you want to use TopLink,not TopLink Essentials.
You then attempt to have the 'toplink.jar' loaded instead of the 'toplink-essentials.jar'. To do this in server.xml you point to the 'toplink.jar' and comment out the reference to 'toplink-essentials.jar' as in below :
When deploying the application, the following error results:
* Dependent class: com.evermind.server.ejb.persistence.PersistenceUnitManagerImpl*
* Loader: oc4j:10.1.3*
* Code-Source: /D:/OC4J_101340/j2ee/home/lib/oc4j-internal.jar*
* Configuration: <code-source> in META-INF/boot.xml in D:\OC4J_101340\j2ee\home\oc4j.jar*
What needs to be done to ensure that Oracle Toplink is used and not Toplink Essentials in iAS 10.1.3.x OC4J?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document