You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Dominique Pfister (JIRA)" <ji...@apache.org> on 2008/02/27 17:51:51 UTC
[jira] Updated: (JCR-1432) Saving a node deletion that has been
modified externally throws a ConstraintViolationException
[ https://issues.apache.org/jira/browse/JCR-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dominique Pfister updated JCR-1432:
-----------------------------------
Attachment: AddModifyTest.java
Test case exposing issue. What happens is:
session2 removes a
session1 adds child b to a
session1 saves
session2 saves
The last line throws a ConstraintViolationException, because save() detects a child node "b" in the local state that does not exist in the transient state and which it therefore consideres removed.
> Saving a node deletion that has been modified externally throws a ConstraintViolationException
> ----------------------------------------------------------------------------------------------
>
> Key: JCR-1432
> URL: https://issues.apache.org/jira/browse/JCR-1432
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: core 1.4.1
> Reporter: Dominique Pfister
> Priority: Minor
> Attachments: AddModifyTest.java
>
>
> Deleting a node "a" and saving its parent might result in a ConstraintViolationException if node "a" has been modified externally, where an InvalidItemStateException with message "item x has been modified externally" would be more intuitive.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.