You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (Jira)" <ji...@apache.org> on 2024/07/25 15:34:00 UTC
[jira] [Assigned] (JCRVLT-763) IdConflictPolicy: improve documentation for CREATE_NEW_ID
[ https://issues.apache.org/jira/browse/JCRVLT-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke reassigned JCRVLT-763:
-------------------------------------
Assignee: Julian Reschke
> IdConflictPolicy: improve documentation for CREATE_NEW_ID
> ---------------------------------------------------------
>
> Key: JCRVLT-763
> URL: https://issues.apache.org/jira/browse/JCRVLT-763
> Project: Jackrabbit FileVault
> Issue Type: Task
> Components: vlt
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
>
> We recently were .... confused while looking at IdConflictPolicy.CREATE_NEW_ID (https://jackrabbit.apache.org/filevault/referenceablenodes.html#Id_Conflict_Policies and https://jackrabbit.apache.org/filevault/apidocs/org/apache/jackrabbit/vault/fs/api/IdConflictPolicy.html).
> Trouble is, this Enum suggests that it's only relevant when there indeed is an ID conflict. However, it is mapped to https://developer.adobe.com/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/javax/jcr/ImportUUIDBehavior.html which also affects nodes where there actually is no ID collision whatsoever.
> I believe it would be hard to change the behaviour at this point, so we should at least improve the documentation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)