EntityManager.detach() Triggers Lazy Loading Into The Persistence Context
(Doc ID 2513239.1)
Last updated on MARCH 16, 2021
Applies to:Oracle TopLink - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
In the mapping hierarchy when you call the ENTITYMANAGER.DETACH() some of the objects remain attached to the peristence context
If you don't call a getter on one part of the object graph, another (merely connected) part won't be detached properly and that leads to "orphan" objects in the persistence context.
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