[
https://issues.apache.org/jira/browse/JCRVLT-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17372074#comment-17372074
]
Konrad Windszus edited comment on JCRVLT-544 at 6/30/21, 3:29 PM:
------------------------------------------------------------------
I am thinking about falling back to {{nt:folder}} for a hardcoded list of
default types. This list of (probably) wrong default types is {{nt:base}} and
{{nt:hierarchyNode}}. WDYT, [~dsuess]?
was (Author: kwin):
I am thinking about falling back to {{nt:folder}} for a hardcoded list of
default types. This list of (probably) wrong default types is {{nt:base}},
{{nt:hierarchyNode}} and {{nt:unstructured}}. WDYT, [~dsuess]?
> Creation of folders based on parent nodetype instead of nt:folder causing
> regression
> ------------------------------------------------------------------------------------
>
> Key: JCRVLT-544
> URL: https://issues.apache.org/jira/browse/JCRVLT-544
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
> Affects Versions: 3.4.4
> Reporter: Dominik Süß
> Priority: Major
>
> The change of JCRVLT-417 makes folder creation fall back to the nodetypes
> declared in the nodetype constraint of the primary type. This can cause
> regressions with existing packages.
> In the given case the nodetype cq:Component allows a child node definition
> with primaryType nt:base (which nt:folder derives from) - yet as nt:base has
> no childNodeDefinitions declared any substructures fail to install. The
> nodeType definition of cq:Component is correct as it "allows" anything
> deriving from nt:base, whereas only the derived nodeTypes open up further
> options like substructures.
> //cc [~kwin] introducing the behavioral change.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
