You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2023/05/17 15:35:00 UTC
[jira] [Commented] (SLING-11885) ResourceResolverFactoryActivator.bindResourceDecorator never called
[ https://issues.apache.org/jira/browse/SLING-11885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723513#comment-17723513 ]
Konrad Windszus commented on SLING-11885:
-----------------------------------------
The problem seems to be that dynamic references are only found in {{OsgiServiceUtil.getMatchingDynamicReferences}} if they are contained in component implementing services. But also components not implementing any services (in this case the ResourceResolverFactoryActivator) might have dynamic references which need to be considered here!
> ResourceResolverFactoryActivator.bindResourceDecorator never called
> -------------------------------------------------------------------
>
> Key: SLING-11885
> URL: https://issues.apache.org/jira/browse/SLING-11885
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: Testing Sling Mock 3.4.4
> Reporter: Konrad Windszus
> Priority: Major
>
> If I register a custom {{ResourceDecorator}} after the Sling Context has been initialized it will not trigger {{ResourceResolverFactoryActivator.bindResourceDecorator(...)}} (https://github.com/apache/sling-org-apache-sling-resourceresolver/blob/master/src/main/java/org/apache/sling/resourceresolver/impl/ResourceResolverFactoryActivator.java#L608) and therefore my {{ResourceDecorator}} will never be called.
> This happens in https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/e2740ca63aac981f40763917a5ec879aa2a75156/bundle/src/test/java/com/adobe/acs/commons/remoteassets/impl/RemoteAssetDecoratorTest.java#L110
--
This message was sent by Atlassian Jira
(v8.20.10#820010)