Hi, On Wed, Jun 8, 2011 at 12:29 PM, Thomas Auinger <[email protected]> wrote: > When you start the test on a missing or empty repo-folder, it works. Running > it a second time doesn’t.
Looks like Jackrabbit gets confused by the transient removeItem() operation that precedes the addNode(). Basically, the problem is not that addNode() + itemExists() wouldn't work, but that the much less common removeItem() + addNode() + itemExists() combination is having trouble. You can avoid the issue by adding a session.save() call after removeItem(). Can you please file a bug report [1] about this behavior? It does't seem too serious as it only occurs when you're dealing with changes within the same transient space, but obviously it would be better if we fixed that. [1] https://issues.apache.org/jira/browse/JCR BR, Jukka Zitting
