This is issue 117.Currently, the spec is inconsistent or unclear in the treatment of close after close in the cases of PM and PMF.
Unclear: The PMF section on close doesn't address close, but does specifically disallow getPersistenceManager and “set methods” and allow “other get methods”. Nothing is said about isClosed, close, add/remove instance lifecycle listener.
Inconsistent with PMF: The PM section on close says that after close completes, all methods except isClosed throw JDOFatalUserException.
Proposal:Change PM to state: all methods except isClosed, close, and getPMF throw JDOFatalUserException.
Change PMF to state: all methods except isClosed, close, and getter methods throw JDOFatalUserException.
Craig On May 23, 2005, at 1:31 AM, [EMAIL PROTECTED] wrote:
This is a JPOX bug. It's due to a close call to a closed PMF.Question: If the PMF is closed and the close is called, is this a nope orJDOUserException? Quoting Michael Bouschen <[EMAIL PROTECTED]>:Hi Michelle, I added a comment to issue JDO-46 including the stacktrace of theNullPointerException thrown by jpox AbstractPersistenceManagerFactory.close.Regards Michael -- Michael Bouschen [EMAIL PROTECTED] Engineering GmbH mailto:[EMAIL PROTECTED] http://www.tech.spree.de/ Tel.:++49/30/235 520-33 Buelowstr. 66 Fax.:++49/30/2175 2012 D-10783 Berlin
Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
