[ https://jira.jboss.org/browse/JBCACHE-1591?page=com.atlassian.jira.plugin... ] Artjom Bitor updated JBCACHE-1591: ---------------------------------- Description: Assume that during a transaction two nodes are created. One of these nodes gets a child node within the same transaction. And at the end of this transaction this node is moved to another one. When transaction commits our expectation is that this node along with the child node is now under the target node. But that is not the case as can be seen from the attached unit test. By debugging the case where everything happens in the same transaction I looked into the source code of org.jboss.cache.commands.write.MoveCommand. The method "moveRecursively()" tries to get the children of the node using its delegate. In this particular case the delegate does not have any child but the node itself does. Either the changes are not yet propagated to the delegate or the lookup of the children is done wrong. Maybe it should go over the invocation context? Is this part of the concept? I hope not... was:Assume that during a transaction two nodes are created. One of these nodes gets a child node within the same transaction. And at the end of this transaction this node is moved to another one. When transaction commits our expectation is that this node along with the child node is now under the target node. But that is not the case as can be seen from the attached unit test. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira