Mailing-List: contact dev-help@sling.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@sling.apache.org
Date: Thu, 2 Mar 2017 17:56:45 +0000 (UTC)
From: "Stefan Seifert (JIRA)" <jira@apache.org>
To: dev@sling.apache.org
Message-ID: <JIRA.13046104.1487958738000.45171.1488477405389@Atlassian.JIRA>
In-Reply-To: <JIRA.13046104.1487958738000@Atlassian.JIRA>
References: <JIRA.13046104.1487958738000@Atlassian.JIRA> <JIRA.13046104.1487958738702@jira-lw-us.apache.org>
Subject: [jira] [Updated] (SLING-6567) BasicObservationReporter ignores
 resource changes for resource providers mounted at specific paths
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 02 Mar 2017 17:56:51 -0000


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

Stefan Seifert updated SLING-6567:
----------------------------------
    Fix Version/s:     (was: Resource Resolver 1.5.16)
                   Resource Resolver 1.5.18

> 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)