[JCRVLT-403] Clarify usage of package type "application" for overlays

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Assignee: Unassigned
• Reporter: Konrad Windszus
• Created: 22/Jan/20 11:28
• Updated: 22/Nov/23 10:35
• Resolved: 06/Apr/21 10:52

Description

According to JCRVLT-170 it is not allowed to use includes or excludes below a filter rule for application packages. This is a pretty common pattern though for including overlays in an apps package to enforce creating the ancestor nodes with the right type.

See also https://issues.apache.org/jira/browse/JCRVLT-170?focusedCommentId=17016199&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17016199

The use case of two different apps packages providing overlays below the same ancestor node should be supported (with both apps packages not knowing anything about each other) and still ensuring that the right node type is being created for ancestors.

There must be a way of enforcing a certain ancestor node type during import and creating it in case it is not yet there, and failing in case if the ancestor is there with a different/incompatible type.

Issue Links

• is caused by: JCRVLT-170 Introduce the concept of package types
• is related to: JCRVLT-733 Allow to enforce ancestor primary and mixin type
• relates to: JCRVLT-417 Intermediate Node Types should be default node type of parent node type definition instead of "nt:folder"
• relates to: JCRVLT-411 PackageTypeValidator: Optionally allow complex filters for "application" packages
• relates to: JCRVLT-413 Clarify documentation about intermediate/ancestor nodes