Return-Path: Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: (qmail 60438 invoked from network); 20 Apr 2009 19:29:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Apr 2009 19:29:23 -0000 Received: (qmail 11308 invoked by uid 500); 20 Apr 2009 19:29:22 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 11243 invoked by uid 500); 20 Apr 2009 19:29:22 -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 11232 invoked by uid 99); 20 Apr 2009 19:29:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Apr 2009 19:29:22 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Apr 2009 19:29:13 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LvzAi-0001Oc-Lt for users@jackrabbit.apache.org; Mon, 20 Apr 2009 12:28:52 -0700 Message-ID: <23143296.post@talk.nabble.com> Date: Mon, 20 Apr 2009 12:28:52 -0700 (PDT) From: SalmasCM To: users@jackrabbit.apache.org Subject: Re: clustering questions In-Reply-To: <23127048.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: salmas@criticalmass.com References: <23127048.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org Thanks for the verification. I do think that it would be nice to have some more details documented. These might include a section on the observation api and how it works with RMI and with clustering. Also, I found out the hard way that when working with multiple workspaces I should do a clone and then subsequent merges. it would be nice to have a document that shows some tips and tricks on how to use multiple workspaces. One issue we have is that we used the XML import feature to import large amounts of legacy data. Of course these were all imported as Strings. When we tried to set node type properties we found that there was no way to unset them or change them. Is it possible for us to 1. Save all our data in the db except these and persist these on the filesystem so that we could change them if needed? 2. We can always skip the xml load utility and import the data using the JR api using booleans and doubles and dates as required. Would this be advisable? I think setting node type properties would be a better thing to do. Some discussion or explanation of these issues would be great as well. Thanks SalmasCM wrote: > > We are deploying a JR implementation which will consist of a JR cluster of > two independent web apps. One is an admin app and the other a consumer web > site. During testing I have been running both on one box. Now that we are > getting closer to production I want to verify that the observation api > will still work if the apps are deployed independently. I am assuming that > the notifications are handled the same way as the journal updates (through > the common db). Please let me know if I am understanding correctly how > clustering works. > > Regards > -- View this message in context: http://www.nabble.com/clustering-questions-tp23127048p23143296.html Sent from the Jackrabbit - Users mailing list archive at Nabble.com.