-
Type: Bug
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: 5.9.4
-
Fix Version/s: QualifiedToSchedule
-
Component/s: Core
-
Tags:
Depending on the order of children returned by getChildern, removeChildren may ends with orphan version.
Suppose there are 3 visible documents :
/doc1 /folder1 /folder1/proxy1
proxy1 point to a version of doc1.
When performing a session.removeChildren("/")
- If doc1 is removed first then the orphan version is not removed from the repository.
- if foder1 is first removed the DefaultVersionRemovalPolicy fire an orphan_versions_to_remove event and removeChildren works fine.