Return-Path: Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: (qmail 11225 invoked from network); 29 Oct 2009 15:25:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 Oct 2009 15:25:51 -0000 Received: (qmail 30768 invoked by uid 500); 29 Oct 2009 15:25:51 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 30736 invoked by uid 500); 29 Oct 2009 15:25:50 -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 30725 invoked by uid 99); 29 Oct 2009 15:25:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Oct 2009 15:25:50 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of aklimets@day.com designates 207.126.148.89 as permitted sender) Received: from [207.126.148.89] (HELO eu3sys201aog103.obsmtp.com) (207.126.148.89) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 29 Oct 2009 15:25:47 +0000 Received: from source ([209.85.222.193]) by eu3sys201aob103.postini.com ([207.126.154.11]) with SMTP ID DSNKSumz5ESI5RPqrnVs5czd32cRZPHBglIG@postini.com; Thu, 29 Oct 2009 15:25:27 UTC Received: by pzk31 with SMTP id 31so1366155pzk.28 for ; Thu, 29 Oct 2009 08:25:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.165.10 with SMTP id n10mr8649rve.72.1256829923446; Thu, 29 Oct 2009 08:25:23 -0700 (PDT) In-Reply-To: <4fe4c4f50910290701k49c6dcb4kfa8edeea136a00fa@mail.gmail.com> References: <4fe4c4f50910281505v7e851946y5b53a5cc0a08a526@mail.gmail.com> <4fe4c4f50910281642o36af88b4y9cc92f8b52ef3527@mail.gmail.com> <4fe4c4f50910290701k49c6dcb4kfa8edeea136a00fa@mail.gmail.com> Date: Thu, 29 Oct 2009 16:25:23 +0100 Message-ID: Subject: Re: workspaces, multiple repositories From: Alexander Klimetschek To: users@jackrabbit.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, Oct 29, 2009 at 15:01, ChadDavis wrote= : > Sure, I'm familiar with those. =A0But I thought Guo meant that > workspaces should be used for branches, which to me sounds like I, as > a developer, am supposed to use a workspace to create the effect of > "branches". =A0This sounds strange to me because I know that the JCR > handles Version Control for me, so why would I have to use workspaces > to do branches? First of all, you are not forced to use versioning (that has to be enabled per node via the mix:versionable mixin). Just use a workspace and use the content hierarchy to separate your apps, content, users, etc. (unix filesystem is a good example). When you start versioning, branching is often not required at all, as it makes versioning more complex. For example, in the context of content management systems, a linear set of versions of a page is often all it needs (and what end-users can still easily understand). That's why JCR 2.0 introduced a simple versioning as well. Now if you do need to do branches, then you have to use a second workspace, which contains a clone of your content data. As part of that cloning, branches will be created for those nodes that are versioned. Regards, Alex --=20 Alexander Klimetschek alexander.klimetschek@day.com