Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 3915 invoked from network); 9 Oct 2008 11:17:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Oct 2008 11:17:06 -0000 Received: (qmail 28341 invoked by uid 500); 9 Oct 2008 11:17:04 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 28317 invoked by uid 500); 9 Oct 2008 11:17:04 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 28306 invoked by uid 99); 9 Oct 2008 11:17:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Oct 2008 04:17:04 -0700 X-ASF-Spam-Status: No, hits=-1999.9 required=10.0 tests=ALL_TRUSTED,DNS_FROM_SECURITYSAGE X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Oct 2008 11:16:08 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4FCDD234C21C for ; Thu, 9 Oct 2008 04:16:44 -0700 (PDT) Message-ID: <875757757.1223551004325.JavaMail.jira@brutus> Date: Thu, 9 Oct 2008 04:16:44 -0700 (PDT) From: "Alexander Klimetschek (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Commented: (JCR-1677) Allow workspace creation over cluster In-Reply-To: <703603072.1216076912023.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/JCR-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638260#action_12638260 ] Alexander Klimetschek commented on JCR-1677: -------------------------------------------- > For example it conflicts with the JackrabbitWorkspace.createWorkspace(String, InputSource) method (see [1]). > The reason why the element in repository.xml is just the default template is to allow different workspace > to be configured differently. Such non-uniform setups are actually fairly common (at least in deployments that I see). I agree with Jukka. My first patch analysis was faulty, supporting different workspace configurations is important. > Allow workspace creation over cluster > ------------------------------------- > > Key: JCR-1677 > URL: https://issues.apache.org/jira/browse/JCR-1677 > Project: Jackrabbit > Issue Type: Improvement > Components: clustering, jackrabbit-core > Reporter: Matej Knopp > Attachments: patch-1677-1.txt, patch-1677-2.txt > > > When workspace is created on cluster node A and then node added to that workspace, the proper event is sent to the journal, but other cluster nodes are not able to process it because they don't have the workspace. > It would be nice to have a configuration option for the cluster to create such workspace automatically (instead of just logging an error) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.