[
https://issues.apache.org/jira/browse/OAK-9546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405641#comment-17405641
]
Marcel Reutegger commented on OAK-9546:
---------------------------------------
bq. Probably there is an issue with the ReferenceEditor
I didn't look into the details, but from reading the description, it must be
something else. The ReferenceEditor only comes into play at step 4.
> Node.getReferences() not working for moved referenceable node
> -------------------------------------------------------------
>
> Key: OAK-9546
> URL: https://issues.apache.org/jira/browse/OAK-9546
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Affects Versions: 1.40.0
> Reporter: Konrad Windszus
> Priority: Major
>
> The references for a moved referenceable node are not returned via
> {{MovedReferenceableNode.getReferences()}}.
> This works find for non-moved referenceable node.
> With Jackrabbit 2 references of moved nodes work fine.
> This can only be triggered with the following sequence of JCR API calls
> 1. create referenceable node
> 2. move node
> 3. create reference to moved node
> 4. {{Session.save()}}
> In case after 2. there is an additional 4. {{Session.save()}} the reference
> is correctly detected. So somehow the reference search index is not properly
> updated when the referenceable node was moved and referenced in the same
> transient session.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
