openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dianne Richards (JIRA)" <>
Subject [jira] Updated: (OPENJPA-1155) BrokerImpl.detachAllInternal() does not detach newly loaded entities
Date Mon, 06 Jul 2009 17:25:14 GMT


Dianne Richards updated OPENJPA-1155:

    Attachment: patch2.txt

Patch2 added with Jeremy's suggestion.

> BrokerImpl.detachAllInternal() does not detach newly loaded entities
> --------------------------------------------------------------------
>                 Key: OPENJPA-1155
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 2.0.0
>            Reporter: Dianne Richards
>            Assignee: Dianne Richards
>             Fix For: 2.0.0
>         Attachments: patch.txt, patch2.txt
> During detach, it is possible for additional entities to be loaded if the openjpa.DetachState
property has been set to "all" or "fetch-groups". These entities may not be included in the
collection of entities that are identified in the BrokerImpl.detachAllInternal() method when
it calls the DetachManager.detachAll(collection) method. Before 2.0, these newly loaded entities
were always detached since the detach processing always cascaded. However, with the 2.0 spec
requirements for cascade, the default behavior no longer cascades. Therefore, there may be
some entities left in the persistence context after this processing occurs. detachAllInternal()
is associated with the clear(), close(), and afterCompletion() operations and it is expected
that the persistence context really be empty. To ensure this, the compatibility option of
cascadeWithDetach will be set to true by detachAllInternal() before calling the DetachManager.detach()

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message