Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 59605 invoked from network); 12 Mar 2009 13:33:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Mar 2009 13:33:14 -0000 Received: (qmail 21047 invoked by uid 500); 12 Mar 2009 13:33:12 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 21018 invoked by uid 500); 12 Mar 2009 13:33:12 -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 20986 invoked by uid 99); 12 Mar 2009 13:33:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Mar 2009 06:33:12 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Mar 2009 13:33:11 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 9D9B0234C046 for ; Thu, 12 Mar 2009 06:32:51 -0700 (PDT) Message-ID: <1926290368.1236864771644.JavaMail.jira@brutus> Date: Thu, 12 Mar 2009 06:32:51 -0700 (PDT) From: "angela (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Updated: (JCR-2004) Update SPI locking to match JCR 2.0 In-Reply-To: <119770901.1236163916270.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/JCR-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated JCR-2004: ------------------------ Attachment: JCR-2004_spi.patch > Update SPI locking to match JCR 2.0 > ----------------------------------- > > Key: JCR-2004 > URL: https://issues.apache.org/jira/browse/JCR-2004 > Project: Jackrabbit Content Repository > Issue Type: Sub-task > Components: jackrabbit-spi, JCR 2.0 > Reporter: angela > Assignee: angela > Attachments: JCR-2004_spi.patch > > > jcr2spi currently uses the JSR 170 way to determine whether a given Session owns the lock by checking of the lock token is null. > with JSR 283 a new Lock method has been defined for this, while on the other hand the lock token is always null for session-scoped > locks. > In addition 283-locking allows to specify a timeout hint and hint about the owner info that should be displayed > for information purpose. > Proposed changes to SPI: > - extend org.apache.jackrabbit.spi.LockInfo to cover the new functionality added with JSR 283 > - add an variant of RepositoryService.lock that allows to specify timeout and owner hint. > Proposed changes to JCR2SPI: > - change jcr2spi to make use of the new functionality and modify the test for session being lock holder. > this mainly affects > > LockOperation > > LockManager impl > > Lock impl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.