[
https://issues.apache.org/jira/browse/SLING-11885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723531#comment-17723531
]
Stefan Seifert commented on SLING-11885:
----------------------------------------
yes, the problem is related to SLING-11668 and earlier findings. the current
osgi-mock implementation does not correctly implement a "component registry"
but only a "service registry" which is conceptional wrong (for historical
reasons). i've it on my todo-list to refactor this and implement it as a
component registry, but did not have time so far. i've loosly planned to do it
within the next months / this year!
> 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 OSGi Mock 3.3.6
> 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)
