openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (OPENJPA-1545) Add new Detach processing
Date Sat, 10 Apr 2010 17:40:41 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Donald Woods resolved OPENJPA-1545.
-----------------------------------

    Resolution: Fixed

Code checked into 2.0.0, so marking it resolved for the release notes.
If more work is required, please open a new issue and link it to this one.

> Add new Detach processing
> -------------------------
>
>                 Key: OPENJPA-1545
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1545
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: performance
>    Affects Versions: 2.0.0-beta2
>            Reporter: Rick Curtis
>            Assignee: Rick Curtis
>             Fix For: 2.0.0
>
>         Attachments: OPENJPA-1545.patch
>
>
> There have been a number of mailing list posts where the net of the post is that someone
doesn't want OpenJPA to detach their Entities because after the commit happens, then are all
going to be gc'd. All of the detach processing ends up being a waste.  I also observed this
same behavior when running some performance tests.
> With this JIRA I'm going to add a new openjpa.DetachState configuration option which
will enable a new, super fast, minimalistic detach approach. This change is targeted at detach
processing that happens due to an AutoDetach. Explicit detaches(ie: em.detach(..) ) will work
as they always have before.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message