Javadogs, I agree. Here's a proposed spec update for 12.6.7:
<proposed>If the parameter instance of deletePersistent() is a detached instance, the method applies to the associated persistent instance. Similarly, if any of the parameter instances of deletePersistentAll() is a detached instance, the method applies to the associated persistent instances. If the class of instances to be deleted implements the delete callback, then the persistent instance is instantiated and the callback is executed.
</proposed> Craig On Feb 6, 2006, at 8:54 AM, Matthew T. Adams wrote:
I would say that yes, this is correct, but what happens if the corresponding persistent instance implements DeleteCallback? I think that the spec should require the implementation to load the persistent instance and call its jdoPreDelete() method, and call any lifecycle listener methods that may be registered to listen for the deletion of objects of the deleted object'sclass. --matthew-----Original Message----- From: Andy Jefferson [mailto:[EMAIL PROTECTED] Sent: Monday, February 06, 2006 8:32 AM To: [email protected]; [EMAIL PROTECTED] Subject: deletePersistent() with a detached object What is the expected behaviour when calling deletePersistent() with a detached object ? Spec section 12.6.7 doesn't explicitly mention it. Since makePersistent() will now take detached objects and persist them, I would probably expect deletePersistent() to perform the deletion of the underlying persistent object (if it is persistent in this datastore). Is this a correct understanding ? Thanks -- Andy
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
