Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 70421 invoked from network); 22 Aug 2008 07:19:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Aug 2008 07:19:48 -0000 Received: (qmail 55101 invoked by uid 500); 22 Aug 2008 07:19:45 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 55090 invoked by uid 500); 22 Aug 2008 07:19:45 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 55079 invoked by uid 99); 22 Aug 2008 07:19:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Aug 2008 00:19:45 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [62.99.145.2] (HELO mx.inode.at) (62.99.145.2) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Aug 2008 07:18:47 +0000 Received: from [195.238.227.52] (port=15624 helo=[10.100.1.147]) by smartmx-02.inode.at with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1KWQvS-0007AJ-Oi for users@jackrabbit.apache.org; Fri, 22 Aug 2008 09:19:14 +0200 Message-ID: <48AE6870.2080707@cosy.sbg.ac.at> Date: Fri, 22 Aug 2008 09:19:12 +0200 From: Martin Mayr User-Agent: Thunderbird 2.0.0.16 (X11/20080724) MIME-Version: 1.0 To: users@jackrabbit.apache.org Subject: versioning checkout timeout Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org i want to block multiple users from editing a file stored with JR through the checkin(), checkout() and isCheckedOut() methods - so if one does a checkout, no one else should be able to get the document until it's checked in again is there a predefined time after which the node looses it's checkedOut status? (so it won't keep the status checkedOut for lets say a whole day ) because my system 'may' encounter problems, if a user doesn't close the session appropiatly and therefore his opened documents stay in checkedOut status martin mayr