Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 13880 invoked from network); 11 Aug 2006 11:45:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 11 Aug 2006 11:45:33 -0000 Received: (qmail 80224 invoked by uid 500); 11 Aug 2006 11:45:32 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 79980 invoked by uid 500); 11 Aug 2006 11:45:31 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 79971 invoked by uid 99); 11 Aug 2006 11:45:31 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Aug 2006 04:45:31 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Aug 2006 04:45:29 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id A0BAD7142D3 for ; Fri, 11 Aug 2006 11:41:15 +0000 (GMT) Message-ID: <21994182.1155296475655.JavaMail.jira@brutus> Date: Fri, 11 Aug 2006 04:41:15 -0700 (PDT) From: "Jukka Zitting (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Updated: (JCR-533) failing Node.lock() might leave inconsistent transient state In-Reply-To: <859026.1154937133912.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/JCR-533?page=all ] Jukka Zitting updated JCR-533: ------------------------------ Fix Version/s: 1.1 Affects Version/s: 0.9 1.0 > a Node.lock() is very like a Node.setProperty(). No, not really. A "transient lock" makes no sense, you always want your locks to affect all sessions. The lock properties on mix:lockable nodes are more like metadata that gives you access to the current locking state of a node, not something you'd modify directly using the normal Item API. > failing Node.lock() might leave inconsistent transient state > ------------------------------------------------------------ > > Key: JCR-533 > URL: http://issues.apache.org/jira/browse/JCR-533 > Project: Jackrabbit > Issue Type: Bug > Components: locks > Affects Versions: 1.0, 1.0.1, 0.9 > Environment: Ubuntu Dapper > Reporter: Paco Avila > Assigned To: Stefan Guggisberg > Fix For: 1.1 > > Attachments: DummyLockAccessDenied.java, MyAccessManagerLockAccessDenied.java > > > When I try to node.lock(true, false) a node and the lock fails due to lak of user privilegies, the lock stay in the user transient session. If a perform a node.refresh(false) the node still is locked in the transient session. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira