[ https://issues.apache.org/jira/browse/SLING-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090251#comment-16090251 ]
Alexander Klimetschek commented on SLING-7014: ---------------------------------------------- [~cziegeler] [~sseif...@pro-vision.de] Could you look into this? If this is the case, it's a critical bug in the resolution logic of the default SPI implementation. Note that {{cq:conf}} is our custom name for the {{sling:configRef}} property. As stated in the [documentation|http://sling.apache.org/documentation/bundles/context-aware-configuration/context-aware-configuration-default-implementation.html]: {quote}Go up in the content resource tree until a resource with sling:configRef is found. This is the 'inner-most' context. Check if a configuration resource exists at the path the property points to.{quote} > Inheritance of configurations from parent content resource > ---------------------------------------------------------- > > Key: SLING-7014 > URL: https://issues.apache.org/jira/browse/SLING-7014 > Project: Sling > Issue Type: Bug > Reporter: Nitin Gupta > Priority: Critical > > configure /content/dam/folder/@cq:conf = /conf/something > Then use the sling context aware API to get the configuration for > /content/dam/folder/asset.png and I essentially get /conf/global (an > osgi-configured fallback) instead of /conf/something -- This message was sent by Atlassian JIRA (v6.4.14#64029)