You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2013/12/20 00:46:07 UTC

[jira] [Commented] (OAK-1300) Removing a reference from a mv property destroys the reverse lookup from the remaining

    [ https://issues.apache.org/jira/browse/OAK-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13853479#comment-13853479 ] 

Tobias Bocanegra commented on OAK-1300:
---------------------------------------

added test: org.apache.jackrabbit.oak.jcr.ReferencesTest#testMVRemoveReferences (disabled in pom.xml)

> Removing a reference from a mv property destroys the reverse lookup from the remaining
> --------------------------------------------------------------------------------------
>
>                 Key: OAK-1300
>                 URL: https://issues.apache.org/jira/browse/OAK-1300
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.13
>            Reporter: Tobias Bocanegra
>             Fix For: 0.14
>
>
> 1. create a mv reference property that has 2 references, ref1 and ref2.
> 2. check if ref1.getReferences() and ref2.getReferences() resolve to the property
> 3. remove the ref1 value from the reference property
> 4. ref2.getReferences() is empty



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)