Apache JDO Project - Issue 135: Duplicate get/setDetachAllOnCommit

This is Interesting: Free IT Magazines  
Home > Archive > Apache JDO Project > October 2005 > Issue 135: Duplicate get/setDetachAllOnCommit





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Issue 135: Duplicate get/setDetachAllOnCommit
Craig L Russell

2005-10-30, 5:45 pm

Javadogs,

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).
</moved>

Comments?

Craig


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!


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com