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

Tue, 27 Feb 2007 03:19:12 -0800

Issue (View Online)

Key: NXP-637
Issue Type: New Feature New Feature
Status: In Progress In Progress
Priority: Critical 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: 27/02/07 12:18   Created: 17/02/07 18:26  

The following work was logged on this issue:

Author: Dragos Mihalache
Date: 27/02/07 12:18
Time Logged: 1 week, 1 day, 2 hours
Work Description:
custom versioning service implementation impacted files: - JCRVersioningService - VersioningService - BuiltinTypes - JCRDocument - CustomDocumentVersion - CustomDocumentVersionIterator - CustomVersioningService - VerServUtils - VersioningService.xml etc

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
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets

Reply via email to