From users-return-9099-apmail-jackrabbit-users-archive=jackrabbit.apache.org@jackrabbit.apache.org Mon Sep 29 12:01:03 2008 Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 55181 invoked from network); 29 Sep 2008 12:01:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Sep 2008 12:01:03 -0000 Received: (qmail 10603 invoked by uid 500); 29 Sep 2008 12:01:00 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 10583 invoked by uid 500); 29 Sep 2008 12:01:00 -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 10572 invoked by uid 99); 29 Sep 2008 12:01:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Sep 2008 05:01:00 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of aklimets@day.com designates 207.126.148.181 as permitted sender) Received: from [207.126.148.181] (HELO eu3sys201aog001.obsmtp.com) (207.126.148.181) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 29 Sep 2008 11:59:59 +0000 Received: from source ([209.85.198.248]) by eu3sys201aob001.postini.com ([207.126.154.11]) with SMTP; Mon, 29 Sep 2008 12:00:31 UTC Received: by rv-out-0708.google.com with SMTP id c5so1895910rvf.34 for ; Mon, 29 Sep 2008 05:00:30 -0700 (PDT) Received: by 10.141.129.14 with SMTP id g14mr2374150rvn.56.1222689630518; Mon, 29 Sep 2008 05:00:30 -0700 (PDT) Received: by 10.140.144.3 with HTTP; Mon, 29 Sep 2008 05:00:30 -0700 (PDT) Message-ID: Date: Mon, 29 Sep 2008 14:00:30 +0200 From: "Alexander Klimetschek" To: users@jackrabbit.apache.org Subject: Re: what elements go with which? (repository.xml) In-Reply-To: <1D3D2E4B-B3E2-4F5B-B34A-9C6B2FA44D2F@vmsinfo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1D3D2E4B-B3E2-4F5B-B34A-9C6B2FA44D2F@vmsinfo.com> X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Sep 25, 2008 at 8:08 PM, Warner Onstine wrote: > What I'm not clear on from the docs is this: > - Do I need to replace the FileSystem in the repository.xml (at the top > level) with an OracleFileSystem? No, this is optional in both normal and clustering setup. > - Do I need to replace the FileSystem in the tag in the > repository.xml with one for the OracleFileSystem No, optional as above > - If I do this do I need to replace this with an appropriate > PersistenceManager (again for Oracle) in the tag Yes, the versioning PM must be "clusterable" as well. You can look at the versioning as a special workspace, so you normally have the same PM configuration as for the normal workspaces (apart from separate location/schemaObjectPrefix). > - Do I need to replace the FileSystem in the workspace.xml (at the top > level) with an OracleFileSystem? No, optional, as in question 1. Actually it is the same as in the repository.xml: The workspace.xml is created when a workspace is created and only used for this workspace. The Workspace section in the repository.xml is used as a template for new workspace.xml files. So if you want to change things for existing workspaces, you have to modify the workspace.xml files of those workspaces (but note that you might loose the "connection" to the data if you point to an empty database schema for example). If you can start from scratch (typically during development), you would delete all workspaces (in db, in workspaces folder incl. the workspace.xml files) and just change the repository.xml file. Regards, Alex -- Alexander Klimetschek alexander.klimetschek@day.com