Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 98497 invoked from network); 4 Oct 2008 17:52:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Oct 2008 17:52:06 -0000 Received: (qmail 81692 invoked by uid 500); 4 Oct 2008 17:52:03 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 81659 invoked by uid 500); 4 Oct 2008 17:52:03 -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 81648 invoked by uid 99); 4 Oct 2008 17:52:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Oct 2008 10:52:03 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED 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; Sat, 04 Oct 2008 17:51:09 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 6A3EC234C213 for ; Sat, 4 Oct 2008 10:51:44 -0700 (PDT) Message-ID: <184438212.1223142704434.JavaMail.jira@brutus> Date: Sat, 4 Oct 2008 10:51:44 -0700 (PDT) From: "Boni Gopalan (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Resolved: (JCR-1784) OCM:The UUID of the collection elements changes on update. In-Reply-To: <1329495827.1223118104281.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-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boni Gopalan resolved JCR-1784. ------------------------------- Resolution: Fixed Fixed with the supplied patch > OCM:The UUID of the collection elements changes on update. > ---------------------------------------------------------- > > Key: JCR-1784 > URL: https://issues.apache.org/jira/browse/JCR-1784 > Project: Jackrabbit > Issue Type: Bug > Affects Versions: 1.5 > Reporter: Boni Gopalan > Fix For: 1.5 > > Attachments: JCR-1784.bonigopalan.patch > > Original Estimate: 3h > Remaining Estimate: 3h > > On ocm.update transaction, the Current implementation of DefaultCollectionConverterImpl recreates the colleciton-element nodes if there is no id field specificaiton. This is completely valid for majority of the cases. But I came across a case where the colleciton element has a uuid field. In this case also what is happening with the current implementation is that it drops all the elements from the old collection-elements and recreates the new ones. The major flip side is that now I am left with brand new UUIDs. I think we should address the uniqueness characteristics specified through UUID also while mapping colleciton elements. > I have a patch and a TestCase to verify the same. I have implemented it only for the digester. If people feel the approach is right I will work out an annotation based testcase as well. I do not think it is going to fail even with annotations. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.