Joel Richard created SLING-4653:
-----------------------------------
Summary: Resource merging properties are ignored if the direct
parent of the read resource does not exist
Key: SLING-4653
URL: https://issues.apache.org/jira/browse/SLING-4653
Project: Sling
Issue Type: Bug
Components: ResourceResolver
Affects Versions: Resource Merger 1.2.8
Reporter: Joel Richard
Priority: Critical
If the parent of one of the merged resources does not exist, but another
resource between the merged resource of the same search path and root has some
resource merging properties attached, these properties are ignored in
MergingResourceProvider because resource.getParent returns null and then it
does not try to traverse to root anymore and therefore does not find these
properties.
Example:
/apps/a with sling:hideChildren=*
/libs/a/b/c
If you try to read /mnt/overlay/a/b, it will return null. On the other hand,
/mnt/overlay/a/b/c will return an unmodified merged resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
