[JIRA] Reopened: (NXP-637) Custom versioning system/storage for JCR-backend

[Florent Guillaume (JIRA NUXEO)]

Issue (View Online) Key: NXP-637 Issue Type: New Feature Status: Reopened Priority: Critical Assignee: Dragos Mihalache Reporter: Florent Guillaume Original Estimate: 1 week, 2 days Remaining Estimate: 6 hours Time Spent: 1 week, 1 day, 2 hours Operations View all View comments View history Custom versioning system/storage for JCR-backend  Updated: 28/02/07 16:17   Created: 17/02/07 18:26   The following issue has been reopened. Author: Florent Guillaume Date: 28/02/07 16:17 Comment: Reopening for one missing but important detail: When the document is deleted from the workspace, its version history must be garbage collected, otherwise it will grow endlessly. Project: Nuxeo Enterprise Platform 5 Components: JCRConnector Affects Versions: 5.0.0 GA Fix Versions: 5.1 M1  Description    The JCR backend must be modified so that an alternate optional scheme can be used to store version: instead of having them managed by JCR's versioning APIs, we'll manage then "by hand" by storing and maintaining them in an special toplevel folder. See http://svn.nuxeo.org/trac/nuxeo/browser/doc/refactoring-jcr-version-storage.odt for a spec. This message was automatically generated by Atlassian JIRA Enterprise Edition, Version: 3.7.2-186 - Bug/feature request. If you think it was sent incorrectly, contact one of this server's administrators.

_______________________________________________
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets