db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig L Russell <Craig.Russ...@Sun.COM>
Subject Negative VOTE Issue 135: Move get/setDetachAllOnCommit to PM
Date Tue, 15 Nov 2005 21:02:30 GMT

There is a duplicate get/setDetachAllOnCommit in Transaction that  
belongs only on PersistenceManager.

In the specification, the get/setDetachAllOnCommit methods were  
defined on both PersistenceManager and Transaction. This was an  
oversight; the method belongs only on PersistenceManager. The  
following text will be moved from the specification in chapter 13 to 12:

<moved from 13.4.2 to 12.6.8>
Detach all instances at transaction commit
If this flag is set to true, then all persistent instances in the  
cache are removed from control of the persistence manager at  
transaction commit. Persistent instances of Detachable classes  
transition to the detached state; persistent instances of non- 
Detachable classes transition to the transient state; transient- 
nontransactional instances transition to transient.
If this flag is set to false, then the instances in the cache are  
transitioned according to the RetainValues flag.
boolean getDetachAllOnCommit();
The value of the DetachAllOnCommit flag is returned.
void setDetachAllOnCommit(boolean flag);
The value of the DetachAllOnCommit flag is set to the parameter  
value. The flag takes effect during the next commit after being  
called. This method is allowed at any time except during transaction  
completion (beforeCompletion and afterCompletion).

Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message