project_key: SOA See linked issue.
Link: Added: This issue depends MODE-1302
The problem is a save hasn't been issued after the node was changed. When the node was changed, the version became 2, and therefore the path changed. The new path was used in the isversionable call, but the path was not found because a save had not been issued yet for the changed node. Resolution: call save after the change and before isversionable is called.
Link: Added: This issue relates to SOA-2863
Van's description is not correct. The stack trace clearly shows that the PathNotFoundException occurs when attempting to locate the node that was created and persisted in an earlier save(). See MODE-1302 for details.
Randall Hauch <rhauch> made a comment on jira MODE-1302 The first thing to do is to create a test case that replicates this (not sure why there isn't one) and verify that we can replicate the problem. We've made quite a few fixes since the 2.5.2 version, so there's no guarantee this is even still a problem. If it still is a problem, maybe one thing to look at is the {{Session.refresh(true)}} call. Perhaps we're losing some transient state somewhere. Marek mentioned the problem occurs with other mixins, which means the basic test case to try might be just adding a mixin and then getting the node by path.
Horia Chiorean <hchiorea> made a comment on jira MODE-1302 The bug was caused by a couple of faults in the session.refresh algorithm, which caused the nodes immediately under root to be added as SNS, in case those nodes had children which had been changed in the session. The issues fixed are: * refresh phase 1 - determining which nodes should be left and which should be discarded * LinkedListMultimap.clear method, which caused refresh phase 2 to incorrectly duplicate existing nodes under a parent, as SNS. This last point was the actual cause of the bug
Horia Chiorean <hchiorea> made a comment on jira MODE-1302 In 3.x, the fix to the LinkedListMultimap is already there, while the refresh algorithm isn't there anymore. Therefore, no work is needed in 3.x for this issue.
Randall Hauch <rhauch> made a comment on jira MODE-1302 Merged into the 'master' branch.
Issue has been fixed in 2.8.
According to https://bugzilla.redhat.com/show_bug.cgi?id=781079#c9 this should be already fixed - moving to ON_QA
Verified on ER2.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: In previous versions, an exception would appear when users attempted to retrieve a node's version history. A "PathNotFoundException" message would appear. As a result, users could not view the requested information. This has been fixed in 5.3.
Randall Hauch <rhauch> updated the status of jira MODE-1302 to Closed