Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 74010 invoked from network); 27 Aug 2006 15:16:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 27 Aug 2006 15:16:46 -0000 Received: (qmail 73300 invoked by uid 500); 27 Aug 2006 15:16:46 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 73123 invoked by uid 500); 27 Aug 2006 15:16: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 73114 invoked by uid 99); 27 Aug 2006 15:16:45 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 27 Aug 2006 08:16:45 -0700 X-ASF-Spam-Status: No, hits=0.8 required=10.0 tests=DNS_FROM_RFC_ABUSE,MAILTO_TO_SPAM_ADDR,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of tobias.strasser@gmail.com designates 64.233.162.201 as permitted sender) Received: from [64.233.162.201] (HELO nz-out-0102.google.com) (64.233.162.201) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 27 Aug 2006 08:16:45 -0700 Received: by nz-out-0102.google.com with SMTP id z3so775355nzf for ; Sun, 27 Aug 2006 08:16:24 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=Cf/h1s1WG/mfEozm21u22m7J9TG+dSTblCqtqfyBzjsBtkvmscx5bmrE4YcSmfhyEKamCIOi00UPXWuVzf+ouEHRHbXjVGoEKnRx1Ms5GkEoFL5Ry9owkkvTNsnVe1asOy6yAtJGLLVxZYrh2FZqTZhth6Qc5e+BBxnbkhBrrqY= Received: by 10.65.73.16 with SMTP id a16mr5708095qbl; Sun, 27 Aug 2006 08:16:24 -0700 (PDT) Received: by 10.64.21.3 with HTTP; Sun, 27 Aug 2006 08:16:24 -0700 (PDT) Message-ID: <8be731880608270816g4c602532r10fe7ffba119dba6@mail.gmail.com> Date: Sun, 27 Aug 2006 17:16:24 +0200 From: "Tobias Bocanegra" Reply-To: tobias.bocanegra@day.com Sender: tobias.strasser@gmail.com To: users@jackrabbit.apache.org Subject: Re: Checking out a node In-Reply-To: <5992432.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <5992432.post@talk.nabble.com> X-Google-Sender-Auth: 4c9c2fc686d35c34 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N versioning != locking if you need concurrect versioning, use seperate workspaces per user or locking. regards, toby On 8/26/06, JavaJ wrote: > > So according to the javadoc, when you check out a node using Node.checkout(), > the isCheckedOut property of that node changes to "true" and all of its > non-versionable child nodes become writeable. These changes are persisted > immediately. I assume this means that the changes are propagated across all > sessions. > > So: > > - UserA retrieves NodeA and immediately checks it out, starts modifying > it... > - Before UserA checks in NodeA, UserB retrieves NodeA > - Can UserB start changing NodeA even though he didn't check it out himself? > If so, can he save or check in the changes? What happens if he saves the > changes before UserA checks in his changes? > > -- > View this message in context: http://www.nabble.com/Checking-out-a-node-tf2167382.html#a5992432 > Sent from the Jackrabbit - Users forum at Nabble.com. > > -- -----------------------------------------< tobias.bocanegra@day.com >--- Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel T +41 61 226 98 98, F +41 61 226 98 97 -----------------------------------------------< http://www.day.com >---