[
https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528529#comment-15528529
]
Carsten Ziegeler edited comment on SLING-6056 at 9/28/16 5:59 AM:
------------------------------------------------------------------
[~egli] We can't make a major version change of that package, we introduced the
new abstract class exactly for that reason: being able to add new functionality
without requiring to update the major version number. If we would increase the
major package version, we break all provder implementations.
I'm not 100% sure the API change is really needed, give me please some days to
think about it.
was (Author: cziegeler):
[~egli] We can't make a major version change of that package, we introduced the
new abstract class exactly for that reason. If we would increase the major
package version, we break all implementations.
I'm not 100% sure the API change is really needed, give me please some days to
think about it.
> 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: JCR Resource 2.8.0, API 2.14.2, Resource Resolver 1.4.18
> Reporter: Stefan Egli
> Assignee: Stefan Egli
> Priority: Critical
> Fix For: JCR Resource 2.8.2, API 2.15.0, Resource Resolver 1.4.20
>
> Attachments: SLING-6056.patch
>
>
> 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)
