[
https://issues.apache.org/jira/browse/JCRVLT-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17372536#comment-17372536
]
Konrad Windszus commented on JCRVLT-544:
----------------------------------------
[~dsuess] First of all the changed behaviour was proposed by [~tripod] and for
a good reason! This has been implemented 5 releases ago(!) so we cannot just
revert. This is open source and Adobe is just one consumer (out of potentially
many). I proposed a PR which fixes your issue. So from my perspective there are
now three options:
1. We can merge the PR as proposed as soon as you add some IT
1. We leave the behaviour in place
1. You come up with an alternative solution
> Creation of folders based on parent's default 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üß
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: 3.5.2
>
>
> 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)
