When a DObject is destroyed, set its oid to -1 so that it knows that it

was once alive but is now gone. Catch attempts to start a transaction on a
destroyed object and log them as such. Made isDestroyed() and isActive()
final for wholly unfounded performance reasons.


git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@3045 542714f4-19e9-0310-aa3c-eee0fc999fb1
This commit is contained in:
Michael Bayne
2004-07-03 07:16:56 +00:00
parent 0be671cd09
commit 90e5231bae
2 changed files with 24 additions and 4 deletions
@@ -1,5 +1,5 @@
//
// $Id: PresentsDObjectMgr.java,v 1.43 2004/06/29 03:22:22 mdb Exp $
// $Id: PresentsDObjectMgr.java,v 1.44 2004/07/03 07:16:56 mdb Exp $
package com.threerings.presents.server;
@@ -400,6 +400,7 @@ public class PresentsDObjectMgr
// inactivate the object
target.setManager(null);
target.setOid(-1);
// deal with any remaining oid lists that reference this object
Reference[] refs = (Reference[])_refs.remove(oid);