openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey (JIRA)" <>
Subject [jira] Updated: (OPENJPA-591) Entities are flushed before being detached or serialized
Date Sun, 25 May 2008 02:41:58 GMT


Patrick Linskey updated OPENJPA-591:

    Fix Version/s:     (was: 1.1.0)

> Entities are flushed before being detached or serialized
> --------------------------------------------------------
>                 Key: OPENJPA-591
>                 URL:
>             Project: OpenJPA
>          Issue Type: Sub-task
>          Components: kernel
>    Affects Versions: 1.0.0, 1.0.1, 1.0.2
>            Reporter: Michael Dick
>            Assignee: Michael Dick
>             Fix For: 1.0.3, 1.1.1, 1.2.0
> Entities are flushed if the entity is serialized or if the detach and detachAll methods
are invoked.
> Similar to OPENJPA-119 I believe this is a remnant of the JDO persistence layer. Whether
this is desirable in JPA or not, we need to be consistent whether the entity is detached via
clear, or the detach methods. 
> To resolve the problem I propose adding a new Compatibility option : flushBeforeDetach.
If this is set to true we'll keep the current JDO-like behavior. If false then we'll just
detach. I believe the same setting could apply when entities are serialized although it might
be clearer to have a separate option for serialization. 
> In the 1.0.x branch the flushBeforeDetach setting will only take effect for the detach,
detachAll and serialization path. It will not affect the EntityManager.clear() method - in
order to maintain backwards compatibility. 
> In 1.2.x + the clear method will also defer to the flushBeforeDetach setting. 

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

View raw message