[ https://issues.apache.org/jira/browse/JCRVLT-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515804#comment-16515804 ]
Timothee Maret commented on JCRVLT-303: --------------------------------------- [~tripod] I have added a failing test in https://github.com/tmaret/jackrabbit-filevault/commit/57503560500d8ba4e8347cd707247fea12af4ba5 > Register namespace under a unique prefix in case of clash > --------------------------------------------------------- > > Key: JCRVLT-303 > URL: https://issues.apache.org/jira/browse/JCRVLT-303 > Project: Jackrabbit FileVault > Issue Type: Improvement > Components: Packaging, vlt > Affects Versions: 3.1.44 > Reporter: Timothee Maret > Priority: Major > > With AEM DAM system, some parts of XMP metadata are backed by JCR namespaces. > An asset may contain metadata which namespace conflicts with already > registered JCR namespace. > Those conflict prevent content packages to be imported, which is a functional > issue for DAM system aiming at ingesting any asset. > This issue is about mitigating namespace conflicts, by generating new > namespaces when they occur. > Assuming a namespace with prefix {{N1}} and URI {{U1}} is already registered. > When importing a content package containing a conflicting namespace with > prefix {{N1}} and URI {{U2}}, instead of failing, we would import the content > with a new namespace prefix {{N1_1}} and URI {{U2}}. -- This message was sent by Atlassian JIRA (v7.6.3#76005)