Relationship between "locked/unlocked" (in the repository) and "checkedin/checkedout"(in cmis)
I need to manage concurrent access to documents in the repository by interactive Nuxeo DM users and programmatic CMIS client applications. Nuxeo DM users use “lock/unlock” operations to manage access to documents while CMIS client applications use “checkin/checkout” operations. It seems like the Nuxeo CMIS Connector should “lock” documents on checkout and “unlock” documents on checkin. Is this currently implemented in the Nuxeo 5.5 CMIS Connector? If not, should I create a JIRA for this issue or does one already exist?
It's not implemented and I didn't find a JIRA for it although this request has already been mentioned somewhere else (the forums maybe?).
 |
Florent Guillaume
Member (36K) 6 8 8 |
04/19/2012 ( History) |
Am I correct that a nuxeo-chemistry patch should prevent a document that is currently "locked" by another user from being either checkedin or checkedOut?
Regarding your question, it depends whether you're talking about pure CMIS operations or a mix of CMIS use and Nuxeo use (Nuxeo can unlock a document without it being checked in for instance).