jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martijn Hendriks (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2138) Prevent persistence of faulty back-references
Date Thu, 11 Jun 2009 08:49:07 GMT

    [ https://issues.apache.org/jira/browse/JCR-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718354#action_12718354
] 

Martijn Hendriks commented on JCR-2138:
---------------------------------------

The patch works in such a way that reference properties with the same id which are added in
two sessions at the same time do not collide (i.e., the last save wins and no exception is
thrown). This is the same behavior as before, except for that the externally added references
are now first removed which keeps the back-reference data in good shape. The alternative is
to throw an ItemStateException. I also tried that but then a versioning related test failed
(the RestoreAndCheckoutTest).

> Prevent persistence of faulty back-references
> ---------------------------------------------
>
>                 Key: JCR-2138
>                 URL: https://issues.apache.org/jira/browse/JCR-2138
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: core 1.4.5, 2.0.0
>            Reporter: Martijn Hendriks
>            Assignee: Martijn Hendriks
>         Attachments: JCR-2138.patch
>
>
> The SharedItemStateManager updates reference data. Sometimes the back-references to reference
properties are not updated correctly with the result that nodes cannot removed anymore. The
attached patch contains JUnit test cases and a possible solution.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message