openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sutter (JIRA)" <j...@apache.org>
Subject [jira] Created: (OPENJPA-422) Calendar objects contained in a detached Entity still have a "live" StateManagerImpl
Date Sat, 27 Oct 2007 19:51:50 GMT
Calendar objects contained in a detached Entity still have a "live" StateManagerImpl
------------------------------------------------------------------------------------

                 Key: OPENJPA-422
                 URL: https://issues.apache.org/jira/browse/OPENJPA-422
             Project: OpenJPA
          Issue Type: Bug
          Components: kernel
    Affects Versions: 1.0.0
            Reporter: Kevin Sutter
            Assignee: Kevin Sutter
             Fix For: 1.0.1, 1.1.0


When Entities are detached, normally the StateManagerImpl instance associated with this Entity
is replaced with a DetachedStateManager.  Not only with the Entity itself, but also with the
proxied attributes (Date, Calendar, Collection, and Map types).  But, somehow the Calendar
object type was forgotten in the code for this processing.  So, the Calendar proxy type was
left with a "live" StateManagerImpl instance.  If the owning Broker (EntityManager) for this
Entity was closed, then the use of this "live" StateManagerImpl would end up with an IllegalStateException.
 And, even if the owning Broker (EntityManager) was still open, this "live" StateManagerImpl
should not have been tracking the state since the enclosing Entity was detached.

A simple one-line update to DetachManager$DetachFieldManager.reproxy() method will now process
the Calendar proxies as well as the other proxies it was already doing.

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


Mime
View raw message