[jira] [Commented] (SLING-6056) achieve 1:1 mapping between observation and resource change listener

[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15585582#comment-15585582 ] Carsten Ziegeler commented on SLING-6056: - Finished the implementation in jcr resource, except for

[jira] [Commented] (SLING-6056) achieve 1:1 mapping between observation and resource change listener

[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15584751#comment-15584751 ] Carsten Ziegeler commented on SLING-6056: - Updated the resource resolver implementation to

[jira] [Commented] (SLING-6056) achieve 1:1 mapping between observation and resource change listener

[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15571325#comment-15571325 ] Carsten Ziegeler commented on SLING-6056: - I've added a new method to the api as discussed above -

[jira] [Commented] (SLING-6056) achieve 1:1 mapping between observation and resource change listener

[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15571302#comment-15571302 ] Carsten Ziegeler commented on SLING-6056: - I had an offline discussion with [~egli] and now I

[jira] [Commented] (SLING-6056) achieve 1:1 mapping between observation and resource change listener

[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529517#comment-15529517 ] Carsten Ziegeler commented on SLING-6056: - :) I understand that you think that method is required

[jira] [Commented] (SLING-6056) achieve 1:1 mapping between observation and resource change listener

[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529403#comment-15529403 ] Stefan Egli commented on SLING-6056: if we have the new method you suggested in ObservationReporter:

[jira] [Commented] (SLING-6056) achieve 1:1 mapping between observation and resource change listener

[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529391#comment-15529391 ] Carsten Ziegeler commented on SLING-6056: - Alright but having the registration of the two

[jira] [Commented] (SLING-6056) achieve 1:1 mapping between observation and resource change listener

[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529346#comment-15529346 ] Stefan Egli commented on SLING-6056: bq. The jcr resource module will register two observers I don't

[jira] [Commented] (SLING-6056) achieve 1:1 mapping between observation and resource change listener

[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529285#comment-15529285 ] Carsten Ziegeler commented on SLING-6056: - Ok, so we can add a new reportChanges method to

[jira] [Commented] (SLING-6056) achieve 1:1 mapping between observation and resource change listener

[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529055#comment-15529055 ] Stefan Egli commented on SLING-6056: bq. So I assume you mean we should avoid this additional

[jira] [Commented] (SLING-6056) achieve 1:1 mapping between observation and resource change listener

[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528972#comment-15528972 ] Carsten Ziegeler commented on SLING-6056: - I start to understand the problem, now a

[jira] [Commented] (SLING-6056) achieve 1:1 mapping between observation and resource change listener

[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528529#comment-15528529 ] Carsten Ziegeler commented on SLING-6056: - [~egli] We can't make a major version change of that

[jira] [Commented] (SLING-6056) achieve 1:1 mapping between observation and resource change listener

[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15525450#comment-15525450 ] Stefan Egli commented on SLING-6056: [~cziegeler], I can't see how it can be done isolated in

[jira] [Commented] (SLING-6056) achieve 1:1 mapping between observation and resource change listener

[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15525170#comment-15525170 ] Carsten Ziegeler commented on SLING-6056: - [~egli] The split up can either be done in

[jira] [Commented] (SLING-6056) achieve 1:1 mapping between observation and resource change listener

[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15523423#comment-15523423 ] Stefan Egli commented on SLING-6056: [~cziegeler], [~radu.cotescu], before I dig too deep into this

[jira] [Commented] (SLING-6056) achieve 1:1 mapping between observation and resource change listener

[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15522765#comment-15522765 ] Stefan Egli commented on SLING-6056: As [~mreutegg]

[jira] [Commented] (SLING-6056) achieve 1:1 mapping between observation and resource change listener

[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15508869#comment-15508869 ] Carsten Ziegeler commented on SLING-6056: - I think this is a separate issue and we have to be

[jira] [Commented] (SLING-6056) achieve 1:1 mapping between observation and resource change listener

[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15506623#comment-15506623 ] Stefan Egli commented on SLING-6056: perhaps this should go on a separate ticket, but related to