Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 50813 invoked from network); 3 Aug 2007 16:15:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Aug 2007 16:15:49 -0000 Received: (qmail 59446 invoked by uid 500); 3 Aug 2007 16:15:47 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 59408 invoked by uid 500); 3 Aug 2007 16:15:47 -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 59364 invoked by uid 99); 3 Aug 2007 16:15:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Aug 2007 09:15:47 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Aug 2007 16:15:14 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 16EF97141F1 for ; Fri, 3 Aug 2007 09:14:53 -0700 (PDT) Message-ID: <25587792.1186157693091.JavaMail.jira@brutus> Date: Fri, 3 Aug 2007 09:14:53 -0700 (PDT) From: "Stefan Guggisberg (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Commented: (JCR-1034) Unable to save session after saving a renamed node In-Reply-To: <5175171.1185375031362.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-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517568 ] Stefan Guggisberg commented on JCR-1034: ---------------------------------------- the real issue is that it is possible to save a renamed node without saving its parent. a ConstraintViolationException should be thrown instead indicating that the parent of a renamed node needs to be saved as well. > Unable to save session after saving a renamed node > -------------------------------------------------- > > Key: JCR-1034 > URL: https://issues.apache.org/jira/browse/JCR-1034 > Project: Jackrabbit > Issue Type: Bug > Components: core > Reporter: Edgar Poce > Assignee: Stefan Guggisberg > Priority: Minor > > TransientRepository repo = new TransientRepository( > "applications/test/repository.xml", "applications/test"); > Session s = repo.login(new SimpleCredentials("test", "".toCharArray())); > if (s.getRootNode().hasNode("parent")) { > s.getRootNode().getNode("parent").remove(); > s.save(); > } > // create parent node > Node parent = s.getRootNode().addNode("parent"); > > // create node to rename > parent.addNode("newnode"); > s.save(); > // rename node > s.move("/parent/newnode", "/parent/renamedNewNode"); > // save renamed node > s.getRootNode().getNode("parent/renamedNewNode").save(); > // try to save session --> FAILS > s.save(); > s.logout(); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.