Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 41516 invoked from network); 23 Apr 2008 20:08:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Apr 2008 20:08:55 -0000 Received: (qmail 46111 invoked by uid 500); 23 Apr 2008 20:08:51 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 46050 invoked by uid 500); 23 Apr 2008 20:08:50 -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 45997 invoked by uid 99); 23 Apr 2008 20:08:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Apr 2008 13:08:50 -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; Wed, 23 Apr 2008 20:08:05 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id DF725234C10A for ; Wed, 23 Apr 2008 13:05:21 -0700 (PDT) Message-ID: <1366229435.1208981121914.JavaMail.jira@brutus> Date: Wed, 23 Apr 2008 13:05:21 -0700 (PDT) From: "Julian Reschke (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Commented: (JCR-1552) Concurrent conflicting property creation sometimes doesn't fail In-Reply-To: <649592264.1208963361350.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-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591769#action_12591769 ] Julian Reschke commented on JCR-1552: ------------------------------------- The example that I started with did that. > Concurrent conflicting property creation sometimes doesn't fail > --------------------------------------------------------------- > > Key: JCR-1552 > URL: https://issues.apache.org/jira/browse/JCR-1552 > Project: Jackrabbit > Issue Type: Bug > Components: jackrabbit-core > Affects Versions: core 1.4.2 > Reporter: Thomas Mueller > Assignee: Stefan Guggisberg > Fix For: 1.5 > > > The following test prints "Success": > Session s1 = ... > Session s2 = ... > s1.getRootNode().setProperty("b", "0"); // init with zero > s1.getRootNode().setProperty("b", (String) null); // delete > s1.save(); > s1.getRootNode().setProperty("b", "1"); > s2.getRootNode().setProperty("b", "2"); > s1.save(); > s2.save(); > System.out.println("Success"); > However if the line marked "... // delete" is commented out, > it fails with the following exception: > javax.jcr.InvalidItemStateException: > cafebabe-cafe-babe-cafe-babecafebabe/{}b: the item cannot be saved > because it has been modified externally. > at org.apache.jackrabbit.core.ItemImpl.getTransientStates(ItemImpl.java:246) > at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:928) > at org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:849) > It should fail in all cases. If we decide it shouldn't fail, it needs to be documented. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.