project_key: SOA See linked issue.
Link: Added: This issue depends MODE-1089
This looks awfully similar to MODE-1114 (BRMS-563), which was fixed (along with MODE-1117 and incorporated into a SOA-P 5.1 patch. Was this retested with that patch (SOA-2976)? If not, can it be? (same comment applied to MODE-1089)
I will take a look at 5.1 GA and let you know.
As mentioned on MODE-1089, I've attempted to replicate the problem reported in MODE-1089 in the 'master' branch by adding a test case that does exactly the same logic as in the issue. (Thanks Marek for an excellent bug report!) However, the new test succeeds. I suspect that this issue was fixed with recent changes to rewrite and improve performance of the system graph for versioning. See MODE-1134 for details.
I just marked MODE-1089 as DONE, assuming it does not need to be ported back to 2.2.1 branch. *_If this is not the case, please reopen_* MODE-1089.
ModeShape committed the project fix in 2.5, and should be in the SOA 5.2 release.
Verified on SOA 5.2.ER2
Temporarily reopened to update release notes.
Release Notes Docs Status: Added: Documented as Resolved Issue Writer: Added: dlesage Release Notes Text: Added: https://issues.jboss.org/browse/SOA-2863 Users would sometimes encounter a PathNotFoundException when trying to check in a node. Updates to the Modeshape software have rectified this issue so users can now check in nodes without encountering any problems.
Link: Added: This issue is related to SOA-3569