You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2021/10/31 09:39:00 UTC

[jira] [Resolved] (SLING-10896) Use service events for detecting adapter changes

     [ https://issues.apache.org/jira/browse/SLING-10896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-10896.
--------------------------------------
    Resolution: Fixed

Changed in https://github.com/apache/sling-org-apache-sling-servlets-resolver/commit/00a2e32791b37ddb3a40a2c8f2ee3b2658dc988e

> Use service events for detecting adapter changes
> ------------------------------------------------
>
>                 Key: SLING-10896
>                 URL: https://issues.apache.org/jira/browse/SLING-10896
>             Project: Sling
>          Issue Type: Improvement
>          Components: Servlets
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: Servlets Resolver 2.8.4
>
>
> The ResolutionCache is currently listening on event admin events for changes in adapter factories. However, support for event admin is only optional for the adapter manager implementation which makes this approach less reliable.
> On the other hand since many years, Adaption services are registers which provides a reliable mechanism. We should use service events instead.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)