[
https://issues.apache.org/jira/browse/JCRVLT-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated JCRVLT-733:
-----------------------------------
Description:
Currently it is impossible to enforce a type for an uncovered ancestor node:
https://jackrabbit.apache.org/filevault/filter.html#Uncovered_ancestor_nodes.
Existing nodes are never touched, and therefore might have an incompatible type
which prevent the actual child node installation.
The workaround outlined e.g. at JCRVLT-403 is to leverage include patterns
which override the full ancestor node (but not arbitrary children). This might
also destroy other properties though (apart from types).
This is necessary whenever two packages might contribute to subtrees sharing a
common ancestor. There is often no dependent package which just provides the
common ancestor (as that would also overwrite the full subtree).
was:
Currently it is impossible to enforce a type for an uncovered ancestor node:
https://jackrabbit.apache.org/filevault/filter.html#Uncovered_ancestor_nodes.
Existing nodes are never touched, and therefore might have an incompatible type
which prevent the actual child node installation.
The workaround outlined e.g. at JCRVLT-403 is to leverage include patterns
which override the full ancestor node (but not arbitrary children). This might
also destroy other properties though (apart from types).
> Allow to enforce ancestor primary and mixin type
> ------------------------------------------------
>
> Key: JCRVLT-733
> URL: https://issues.apache.org/jira/browse/JCRVLT-733
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Reporter: Konrad Windszus
> Priority: Major
>
> Currently it is impossible to enforce a type for an uncovered ancestor node:
> https://jackrabbit.apache.org/filevault/filter.html#Uncovered_ancestor_nodes.
> Existing nodes are never touched, and therefore might have an incompatible
> type which prevent the actual child node installation.
> The workaround outlined e.g. at JCRVLT-403 is to leverage include patterns
> which override the full ancestor node (but not arbitrary children). This
> might also destroy other properties though (apart from types).
> This is necessary whenever two packages might contribute to subtrees sharing
> a common ancestor. There is often no dependent package which just provides
> the common ancestor (as that would also overwrite the full subtree).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
