openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Evan Ireland" <eirel...@sybase.com>
Subject RE: [jira] Resolved: (OPENJPA-422) Calendar objects contained in a detached Entity still have a "live" StateManagerImpl
Date Sun, 28 Oct 2007 20:05:15 GMT
Kevin,

Since you appear to be familiar with the proxying stuff, I 
wonder if you can say, for persistent attributes of type
"byte[]" which cannot be proxied, but are mutable,
how does OpenJPA handle that case?

> -----Original Message-----
> From: Kevin Sutter (JIRA) [mailto:jira@apache.org] 
> Sent: Sunday, 28 October 2007 9:22 a.m.
> To: dev@openjpa.apache.org
> Subject: [jira] Resolved: (OPENJPA-422) Calendar objects 
> contained in a detached Entity still have a "live" StateManagerImpl
> 
> 
>      [ 
> https://issues.apache.org/jira/browse/OPENJPA-422?page=com.atl
> assian.jira.plugin.system.issuetabpanels:all-tabpanel ]
> 
> Kevin Sutter resolved OPENJPA-422.
> ----------------------------------
> 
>     Resolution: Fixed
> 
> Resolved for 1.0.1 and 1.1.0 via svn revision 589207.
> 
> > 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