You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Justin Edelson (JIRA)" <ji...@apache.org> on 2017/03/07 14:36:38 UTC
[jira] [Closed] (SLING-6567) BasicObservationReporter ignores
resource changes for resource providers mounted at specific paths
[ https://issues.apache.org/jira/browse/SLING-6567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Edelson closed SLING-6567.
---------------------------------
> BasicObservationReporter ignores resource changes for resource providers mounted at specific paths
> --------------------------------------------------------------------------------------------------
>
> Key: SLING-6567
> URL: https://issues.apache.org/jira/browse/SLING-6567
> Project: Sling
> Issue Type: Bug
> Components: ResourceResolver
> Affects Versions: Resource Resolver 1.5.14
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Critical
> Fix For: Resource Resolver 1.5.18
>
> Attachments: SLING-6567.patch
>
>
> with the new resource provider SPI an intelligent ResourceListener mechanism was introduced which allows to generate and route resource change events only when a listener is actual interested in this change. this works well when the resource provider is a root provider mounted at {{/}}.
> however this currently fails when an additional resource provider is mounted at a specific path - e.g. at {{/apps/app1}}. in this case listeners mounted to specific glob patterns like {{glob:/apps/**/*.html}} get the changes reported by the resource provider, but listeners registered to {{/}} do not.
> this is a severe problem as some listeners like the script resolution cache are registered to {{/}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)