How TopLink handles deletion of dependent objects

Question

Hi,
If you load an object in one ClientSession, release this Session then serialize this object to Client, in Client remove one dependent object (1-M) from this object, then serialize this to server, on server acquire another ClientSession, acquire an UnitOfWork then register and deepMergeClone the object, the TopLink don't delete the dependent object from database but remove this from cache, what happen?

Answer 1

Are you sure it's mapped as a private relationship on the 1-M? Are you sure that when you remove the target from the collection that you are setting it's source to null? I.e:
In Invoice:
public removeInvoiceItem(InvoiceItem ii) {
getMyInvoiceItems().remove(ii);
ii.setInvoice(null);
When removing a 1-M, it's most important to set the backreference to null.
Are you certain that you are doing the remove on a serialized object and not on the cached object by accident?
- Don