[
https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15525450#comment-15525450
]
Stefan Egli commented on SLING-6056:
------------------------------------
[~cziegeler], I can't see how it can be done isolated in sling.jcr.resource - I
think it requires an api change in sling.api ({{List<ObservationReporter>
getObservationReporter()}}), which propagates to various other bundles as it
means a version increase. But it is necessary since ObservationReporter is the
one containing {{reportChanges}} - and the goal is to have the
Jcr/OakResourceListener directly call the 'correct' reportChanges - ie a 1:1
mapping between Jcr/OakResourceListener and ObservationReporter. And that can
only be achieved (AFAICS) by changing the api..
> achieve 1:1 mapping between observation and resource change listener
> --------------------------------------------------------------------
>
> Key: SLING-6056
> URL: https://issues.apache.org/jira/browse/SLING-6056
> Project: Sling
> Issue Type: Task
> Components: ResourceResolver
> Affects Versions: Resource Resolver 1.4.18
> Reporter: Stefan Egli
> Assignee: Stefan Egli
> Priority: Critical
> Fix For: Resource Resolver 1.4.20
>
>
> At the moment it seems there is a 1:n mapping between 1 OakResourceListener
> (and 1 BasicObservationReporter) and n ResourceChangeListeners. The idea
> however is to get rid of such a bottleneck and have a 1:1 mapping (that might
> or might not be in the BasicObservationReporter, that I don't know). We
> should implement such a 1:1 mapping.
> See [thread on dev list|http://sling.markmail.org/thread/uwhda777psgklwo6]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
