[jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1060) Tutorial - removing a child node from the root still leaves the node in memory
Galder Zamarreno (JIRA)
jira-events at lists.jboss.org
Mon May 21 16:07:53 EDT 2007
[ http://jira.jboss.com/jira/browse/JBCACHE-1060?page=all ]
Galder Zamarreno resolved JBCACHE-1060.
---------------------------------------
Resolution: Done
[JBCACHE-1060] Removed implicit increation of adding child node to root if a node does not exist.
nodeCreated() now executes in the same running thread to avoid scroll to visible path concurrency
issues. nodeCreated() does not access back the cache, so this shouldn't lead to any deadlock issues.
> Tutorial - removing a child node from the root still leaves the node in memory
> ------------------------------------------------------------------------------
>
> Key: JBCACHE-1060
> URL: http://jira.jboss.com/jira/browse/JBCACHE-1060
> Project: JBoss Cache
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 2.0.0.CR1
> Reporter: Galder Zamarreno
> Assigned To: Galder Zamarreno
> Priority: Minor
> Fix For: 2.0.0.CR2
>
>
> I have reproduced an issue via the tutorial but I'm not sure whether it's a tutorial or cache issue yet.
> Making a note of the steps so that I can come back to it later.
> 1st GUI:
> bsh % childFqn2 = Fqn.fromString("/child2");
> </child2>
> bsh % childFqn3 = Fqn.fromString("/child2/child3");
> </child2/child3>
> bsh % child2 = root.addChild(childFqn2);
> <UnversionedNode[ /child2 data=[]]>
> bsh % child3 = root.addChild(childFqn3);
> <UnversionedNode[ /child2/child3 data=[]]>
> 2nd GUI:
> bsh % childFqn2 = Fqn.fromString("/child2");
> </child2>
> bsh % child2 = root.getChild(childFqn2);
> <UnversionedNode[ /child2 data=[] child=[UnversionedNode[ /child2/child3 data=[]]]]>
> bsh % child2.put("key3", "value3");
> <null>
> - Click on child2 in the 2nd GUI
> bsh % child2.clearData();
> 1st GUI:
> bsh % child2.put("key3", "value3");
> <null>
> bsh % root.removeChild(childFqn2);
> <true>
> child2 node is still in memory which shouldn't.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list