[ https://issues.apache.org/jira/browse/JCR-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christophe Lombart resolved JCR-922. ------------------------------------ Resolution: Fixed > jcr mapping layer (OCM) should expose lock owner > ------------------------------------------------ > > Key: JCR-922 > URL: https://issues.apache.org/jira/browse/JCR-922 > Project: Jackrabbit > Issue Type: Improvement > Components: jcr-mapping > Reporter: ruchi goel > Assignee: Christophe Lombart > Fix For: 1.4 > > > jcr mapping layer 's persistencemanager.java does not expose an API for > returning lockowner. Ideally , the following method > public String lock(final String absPath, final boolean isDeep, final boolean > isSessionScoped) > should return a hashmap/String array containing locktoken as well as > lockowner. > I tried having lockowner as a field in my java object and mapping it to > jcr:lockOwner , so that I can just use getLockOwner() . But the problem is > this property gets introduced in the node only if the node is locked. So, > when I try to insert a node , before I can even lock it , the insertion fails > since there is no property like jcr:lockOwner till then . > So, I feel there is need for the above API. It is ok to have it exposed via > separate call in order to maintain backward compatability -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.