Relationships Between JPA 2.0 Cachable(false) And Cachable(true) Entities Should Be Supported
(Doc ID 1464651.1)
Last updated on OCTOBER 18, 2021
Applies to:
Oracle TopLink - Version 11.1.1.4.0 to 11.1.1.5.0 [Release Oracle11g]Information in this document applies to any platform.
Symptoms
There are two entities, the first one with @Cacheable(true) and the other @Cacheable(false). There is a relationship between these JPA 2.0 cachable(false) and cachable(true) entities.
While using TopLink Grid 11.1.1.4.0, following bug is hit:
EclipseLink Bug 232063 - Relationships between JPA 2.0 Cachable(false) and Cachable(true) Entities should be supported
https://bugs.eclipse.org/bugs/show_bug.cgi?id=232063
Error:
Local Exception Stack: Exception [EclipseLink-195] (Eclipse Persistence Services - 2.1.2.v20101206-r8635):
org.eclipse.persistence.exceptions.DescriptorException Exception
Description: The shared class <Class name> must not reference the isolated class xxx.xxx.xxx.
Mapping: org.eclipse.persistence.mappings.OneToOneMapping[null] Descriptor:
RelationalDescriptor(package.<CLASS NAME> -->
[DatabaseTable(<TABLE NAME>)])
at org.eclipse.persistence.exceptions.DescriptorException.isolateDescriptorReferencedBySharedDescriptor(DescriptorException.java:888)
at org.eclipse.persistence.mappings.ForeignReferenceMapping.initializeReferenceDescriptor(ForeignReferenceMapping.java:1063)
at org.eclipse.persistence.mappings.ForeignReferenceMapping.initialize(ForeignReferenceMapping.java:1037)
at org.eclipse.persistence.mappings.OneToOneMapping.initialize(OneToOneMapping.java:998)
at org.eclipse.persistence.internal.queries.MappedKeyMapContainerPolicy.initialize(MappedKeyMapContainerPolicy.java:530)
at org.eclipse.persistence.mappings.DirectCollectionMapping.initialize(DirectCollectionMapping.java:1372)
at org.eclipse.persistence.mappings.DirectMapMapping.initialize(DirectMapMapping.java:320)
at org.eclipse.persistence.descriptors.ClassDescriptor.initialize(ClassDescriptor.java:2659)
at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.initializeDescriptors(DatabaseSessionImpl.java:448)
at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.initializeDescriptors(DatabaseSessionImpl.java:406)
at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.postConnectDatasource(DatabaseSessionImpl.java:666)
at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:615)
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:228)
at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:389)
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.getServerSession(EntityManagerFactoryImpl.java:164)
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:221)
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:209)
. . .
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |