[jira] [Commented] (SLING-5162) Support for the new observation API in the resource resolver

["Tomek Rękawek (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-5162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960696#comment-14960696 ] 

Tomek Rękawek commented on SLING-5162:
--------------------------------------

[~cziegeler], [~egli], maybe we move the discussion about the OSGi bridge here. So, in the SLING-4751 comment, Carsten proposed we remove the OSGi bridge completely. It seems a bit radical - all applications listening to OSGi events for JCR modifications will break. Rewriting them to the new API may not be trivial - there is over 70 such listeners in the latest AEM code. Maybe we can start with marking the {{TOPIC_RESOURCE_*}} as deprecated?

> Support for the new observation API in the resource resolver
> ------------------------------------------------------------
>
>                 Key: SLING-5162
>                 URL: https://issues.apache.org/jira/browse/SLING-5162
>             Project: Sling
>          Issue Type: Sub-task
>          Components: ResourceResolver
>            Reporter: Tomek Rękawek
>             Fix For: Resource Resolver 1.2.8
>
>         Attachments: SLING-5162.patch
>
>
> Add a whiteboard service that listens to all ResourceChangeListener registrations and informs them about modifications. Also, create an OsgiObservationBridge that will convert the new API changes into OSGi events (it will be discussed whether the bridge is necessary).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)