[
https://jira.nuxeo.org/browse/NXP-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexandre Russel updated NXP-5132:
----------------------------------
Description:
we should be able to lock a document accross cluster:
lockservice.lock(docref)
lockservice.lock(docref,, timeout)
Lock should be an object from which we should be able to know:
- the locked document
- the principal who locked
- the server that locked
was:
we should be able to lock a document accross cluster:
lockservice.lock(docref, blockingboolean)
lockservice.lock(docref, blockingboolean, timeout)
Lock should be an object from which we should be able to know:
- the locked document
- the principal who locked
- the server that locked
> lock should work accross cluster
> --------------------------------
>
> Key: NXP-5132
> URL: https://jira.nuxeo.org/browse/NXP-5132
> Project: Nuxeo Enterprise Platform
> Issue Type: Improvement
> Reporter: Alexandre Russel
>
> we should be able to lock a document accross cluster:
> lockservice.lock(docref)
> lockservice.lock(docref,, timeout)
> Lock should be an object from which we should be able to know:
> - the locked document
> - the principal who locked
> - the server that locked
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
