Return-Path: X-Original-To: apmail-jackrabbit-oak-dev-archive@minotaur.apache.org Delivered-To: apmail-jackrabbit-oak-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 113F498FD for ; Mon, 25 Jun 2012 13:47:43 +0000 (UTC) Received: (qmail 98576 invoked by uid 500); 25 Jun 2012 13:47:43 -0000 Delivered-To: apmail-jackrabbit-oak-dev-archive@jackrabbit.apache.org Received: (qmail 98546 invoked by uid 500); 25 Jun 2012 13:47:42 -0000 Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: oak-dev@jackrabbit.apache.org Delivered-To: mailing list oak-dev@jackrabbit.apache.org Received: (qmail 98536 invoked by uid 99); 25 Jun 2012 13:47:42 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jun 2012 13:47:42 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id B9AD814002D for ; Mon, 25 Jun 2012 13:47:42 +0000 (UTC) Date: Mon, 25 Jun 2012 13:47:42 +0000 (UTC) From: "Jukka Zitting (JIRA)" To: oak-dev@jackrabbit.apache.org Message-ID: <1774073038.50950.1340632062765.JavaMail.jiratomcat@issues-vm> In-Reply-To: <812203140.50771.1340628402700.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (OAK-150) Basic JCR LockManager support MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OAK-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400477#comment-13400477 ] Jukka Zitting commented on OAK-150: ----------------------------------- In revision 1353536 I added a basic LockManager implementation and a naive locking implementation that simply uses the presence of the jcr:lockOwner and jcr:lockIsDeep properties to determine whether a node is locked or not. No synchronization or even validation of locking status is present for now. > Basic JCR LockManager support > ----------------------------- > > Key: OAK-150 > URL: https://issues.apache.org/jira/browse/OAK-150 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: jcr > Reporter: Jukka Zitting > Assignee: Jukka Zitting > Labels: locking > > Even though we currently don't (and perhaps never will) support full JCR locking functionality in Oak, it would still be good to have a basic LockManager implementation for clients that assume it's present and use it simply to access lock tokens and to ask whether a particular node is locked or not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira