[ 
https://issues.apache.org/jira/browse/JCR-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619491#action_12619491
 ] 

Claus Köll commented on JCR-1702:
---------------------------------

as i can see are there 2 instances of CachingHierarchyManager

on the testRootNode.addNode(nodeName1, testNodeType) operation there will be 
the first instance be informed with nodeAdded and will store the path and 
nodeid.

on commit() then the second one will be called and so it has the fisrt created 
nodeid not in his idcache.




> Unable to create/lock Node in one Transaction
> ---------------------------------------------
>
>                 Key: JCR-1702
>                 URL: https://issues.apache.org/jira/browse/JCR-1702
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: transactions
>    Affects Versions: core 1.4.5
>            Reporter: Claus Köll
>
> If i try to add a node and then add a lock on it inside one transaction i get 
> a exception

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to