> He may want to purge intermediate work versions of documents between > each release (VersionGistory.removeVersion() is perfect for that), but > also delete a document *and all its past revisions*, due to some legal > requirements. For this last point, it seems JCR lacks a few > functionnalities, as you also point out.
hi cederic, since the creation of a VersionHistory is triggered by the creation of a mix:versionable node, the removal should happen automatically, as soon as no references to that version histroy exist anymore. this is the case, when all mix:versionable nodes (in all workspaces) belonging to that VH are deleted, and all the versions in the VH are removed i.e. only the jcr:rootVersion is left. IMO, it is then safe to delete the version history aswell. i created a jira issue for this [JCR-134]. cheers, tobi -- ------------------------------------------< [EMAIL PROTECTED] >--- Tobias Strasser, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel T +41 61 226 98 98, F +41 61 226 98 97 -----------------------------------------------< http://www.day.com >---
