[
https://issues.apache.org/jira/browse/JCRVLT-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17400456#comment-17400456
]
Konrad Windszus commented on JCRVLT-551:
----------------------------------------
[~tripod] Any idea how JR2/Oak ensures referential integrity for the case that
{{node-a}} existed with {{jcr:uuid=a}} before with some (non weak) references
to it and is now replaced by {{node-a}} with {{jcr:uuid=b}} during the import?
> Set jcr:uuid to value from package when overwriting referenceable node
> ----------------------------------------------------------------------
>
> Key: JCRVLT-551
> URL: https://issues.apache.org/jira/browse/JCRVLT-551
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: vlt
> Affects Versions: 3.5.0
> Reporter: Konrad Windszus
> Priority: Major
>
> Currently the code at
> https://github.com/apache/jackrabbit-filevault/blob/ac74458a0226eb503d96cf2b238cec78b6f36dc2/vault-core/src/main/java/org/apache/jackrabbit/vault/fs/impl/io/DocViewSAXImporter.java#L809
> does not try to adjust the {{jcr:uuid}} property in case a referenceable
> node is imported from a package which already exists with a different
> {{jcr:uuid}} in the repository.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
