Fix bug in HopObject.remove() where we prematurely call unset().
The right thing *seems* to be to actually always call removeNode on the node's parent.
This commit is contained in:
parent
262ba9d5e3
commit
75c7dff23b
1 changed files with 1 additions and 6 deletions
|
@ -720,7 +720,6 @@ public final class Node implements INode, Serializable {
|
|||
|
||||
if (pn != null) {
|
||||
setParent((Node) pn);
|
||||
// anonymous = !pinfo.named;
|
||||
lastParentSet = System.currentTimeMillis();
|
||||
|
||||
return pn;
|
||||
|
@ -1189,11 +1188,7 @@ public final class Node implements INode, Serializable {
|
|||
checkWriteLock();
|
||||
|
||||
try {
|
||||
if (!anonymous) {
|
||||
getParent().unset(name);
|
||||
} else {
|
||||
getParent().removeNode(this);
|
||||
}
|
||||
getParent().removeNode(this);
|
||||
} catch (Exception x) {
|
||||
return false;
|
||||
}
|
||||
|
|
Loading…
Add table
Reference in a new issue