-
Bug
-
Resolution: Done
-
Major
-
5.3.0.Final
-
None
When using ModeShape's API and attempting to remove all the version histories of a node via the org.modeshape.jcr.api.version.VersionManager interface, a referential integrity constraint of the form:
org.modeshape.jcr.cache.ReferentialIntegrityException: Cannot remove some nodes because they are still strongly referred by existing nodes: {/{http://www.jcp.org/jcr/1.0}system/{http://www.jcp.org/jcr/1.0}versionStorage/{}53/{}63/{}2f/{}53632fb320c5312a4f98cfea0221d86bab739ec1=[/{http://www.jcp.org/jcr/1.0}system/{http://www.jcp.org/jcr/1.0}versionStorage/{}ef/{}d1/{}ce/{}efd1ce92b033299879aa009fabc40f49cc7f22d4/{}1.0/{http://www.jcp.org/jcr/1.0}frozenNode/{}testNeu, /{http://www.jcp.org/jcr/1.0}system/{http://www.jcp.org/jcr/1.0}versionStorage/{}ef/{}d1/{}ce/{}efd1ce92b033299879aa009fabc40f49cc7f22d4/{}1.1/{http://www.jcp.org/jcr/1.0}frozenNode/{}testNeu]}
at org.modeshape.jcr.cache.document.WritableSessionCache.persistChanges(WritableSessionCache.java:1433)
at org.modeshape.jcr.cache.document.WritableSessionCache.save(WritableSessionCache.java:701)
at org.modeshape.jcr.JcrVersionManager.remove(JcrVersionManager.java:1056)
is raised if the parent of the node in question is versionable and has multiple versions of the child subgraph.
