New Object Created And Deleted In Nested UnitOfWork Is Commited To Database
(Doc ID 2641422.1)
Last updated on MARCH 10, 2020
Applies to:Oracle TopLink - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
New Object created and deleted in nested UnitOfWork is commited to the database
EL bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=548627 filed.
- UOW of work has an employee from Employee table, and he has one contact.
2. Nested UOW creates a new contact for the employee. Now NUOW has 2 contacts for the employee.
3. NUOW deletes ALL contacts of the employee, and also the employee object using the below
uowN.deleteObject(<OBJECT NAME>N); (<----deleting here, no issue found)
4. after the above statements. First level UOW is also committed.
1. Expected outcome after step 3 is that the employee (from first level UOW) should have 0 contacts.
2. Even after step 4(i.e. committing first level UOW) - the employee is deleted from Employee table. However there 2 problems here:
a. Test code still shows 2 contacts for the employee. Should be 0.
b. Contact table still has reference to the employee. Here original customer id is replaced and a new customer id is inserted into the table. This is incorrect.
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