Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 64994 invoked from network); 22 Feb 2007 11:58:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Feb 2007 11:58:27 -0000 Received: (qmail 71399 invoked by uid 500); 22 Feb 2007 11:58:35 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 71372 invoked by uid 500); 22 Feb 2007 11:58:35 -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 71362 invoked by uid 99); 22 Feb 2007 11:58:35 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Feb 2007 03:58:35 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of jukka.zitting@gmail.com designates 66.249.92.173 as permitted sender) Received: from [66.249.92.173] (HELO ug-out-1314.google.com) (66.249.92.173) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Feb 2007 03:58:24 -0800 Received: by ug-out-1314.google.com with SMTP id p31so88693ugc for ; Thu, 22 Feb 2007 03:58:03 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pN94K5WhPloE/1cwNsKzX9Wd1ag5PHr4WVskqew1stjbspsQA8yuey+1otAHalg5sLmuAxByIYUFsu66bQqE4dqyCBoOq15jjN6sBnfM54Pa7dNuQDcpjfglCG1Eh3RXow7OmibUYfq5Ic4ks+Su0P6iC6EOsVzhW33TC9ZfUrE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WwOw34gQmbLdXISPRIidHJHH1DUOVRfuCzI219sqd6aAq8y9ABx77nPeIWZnkHHY0YYf2qLJ1PBOcyTzQJjtx+clW8c88ERkIZAgq/hiJ6y2BX33Oxy0QbAhpfpRtcCuH4VMti3Vu2JfOZIpAToHkhkfdSApVPs/ilksKRi4BK8= Received: by 10.78.139.1 with SMTP id m1mr42990hud.1172145482774; Thu, 22 Feb 2007 03:58:02 -0800 (PST) Received: by 10.78.106.19 with HTTP; Thu, 22 Feb 2007 03:58:02 -0800 (PST) Message-ID: <510143ac0702220358s3d416c92s1ec4f8f6b71e1d52@mail.gmail.com> Date: Thu, 22 Feb 2007 13:58:02 +0200 From: "Jukka Zitting" To: dev@jackrabbit.apache.org Subject: Re: JCR-465 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Checked: Checked by ClamAV on apache.org Hi, On 2/15/07, Yusuf M wrote: > I would like to start contributing to the jackrabbit project and the issue > (http://issues.apache.org/jira/browse/JCR-465) seems like an easy first > step to accomplish. I would appreciate any help from people along the way. > My first question is: What is the use case for being able to change the > workspace name and do people think its a good function to have? I'm actually not sure about whether introducing a rename method is an easy thing to do. The rename operation is a bit tricky as the workspace name can be embedded in various places like table names used by the database persistence managers, etc. I think an easier operation that we would definitiely appreciate would be to introduce a method to delete a workspace. Deleting a workspace should be much simpler than renaming, and assuming a proper backup/restore tool you can even use the delete operation togethere with createWorkspace() to achieve the use case of renaming a workspace. BR, Jukka Zitting