From users-return-2162-apmail-jackrabbit-users-archive=jackrabbit.apache.org@jackrabbit.apache.org Wed Feb 07 15:25:50 2007 Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 92605 invoked from network); 7 Feb 2007 15:25:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Feb 2007 15:25:50 -0000 Received: (qmail 71347 invoked by uid 500); 7 Feb 2007 15:25:56 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 71333 invoked by uid 500); 7 Feb 2007 15:25:56 -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 71324 invoked by uid 99); 7 Feb 2007 15:25:56 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Feb 2007 07:25:56 -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.175 as permitted sender) Received: from [66.249.92.175] (HELO ug-out-1314.google.com) (66.249.92.175) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Feb 2007 07:25:46 -0800 Received: by ug-out-1314.google.com with SMTP id m3so215206uge for ; Wed, 07 Feb 2007 07:25:25 -0800 (PST) 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=VlAvxu5sfggZ+HCQ6u0Jjii3gwxvmY4//LVBojskxXN/NwcJnNg4mjOyttk4Ph9z32hB7h8o74wbovpknbMQ63ub5M7QvrSsHFU06I66/MVIN3Pl8ItLm30HnzStkf188+8O7lDEE8IPwNlrOliiAsKBxZjhqQTaos8UEAM8OqM= Received: by 10.78.180.18 with SMTP id c18mr508971huf.1170861845453; Wed, 07 Feb 2007 07:24:05 -0800 (PST) Received: by 10.78.177.10 with HTTP; Wed, 7 Feb 2007 07:24:05 -0800 (PST) Message-ID: <510143ac0702070724i3fa0c5c9xf2017a1b3188e888@mail.gmail.com> Date: Wed, 7 Feb 2007 17:24:05 +0200 From: "Jukka Zitting" To: users@jackrabbit.apache.org Subject: Re: NodeTypeRegistry.checkForReferencesInContent() In-Reply-To: <8844504.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8054782.post@talk.nabble.com> <510143ac0612270732i3ce3b1cey503fcf5f9e8a2070@mail.gmail.com> <8074790.post@talk.nabble.com> <459D6F85.8010609@gmx.de> <8768745.post@talk.nabble.com> <8793775.post@talk.nabble.com> <8be731880702040842t6fc92949q933a761e30bd313c@mail.gmail.com> <8796602.post@talk.nabble.com> <8844504.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org Hi, On 2/7/07, anton_slutsky wrote: > So what do you guys think of my implementation? I really hate to deploy my > apps with customized code. I'd rather have it out there with an > out-of-the-box jackrabbit. Looks cool, though I have some concerns. My main concern is about using search to find the node type references. Normally this shouldn't be a problem, but since the search index is a separate copy of the persisted content there is a chance of coherence issues. More notably the search engine is pluggable and in some cases it has been disabled alltogether. Using the actual item state and persistence managers to look for references would IMHO be safer, though as of now there are no access paths outside the search index that would perform reasonably. Another concern is concurrency. How can we make sure that there are no concurrent modifications going on that might introduce new references to the node type in question? I think your patch is a good starting point but we still need work to sort out all the relevant details. You may want to attach your patch to JCR-322 or file it as a separate improvement request. I'd also suggest that you take this thread to the developer mailing list. BR, Jukka Zitting