You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2016/01/28 15:12:39 UTC

[jira] [Resolved] (SLING-5169) Deprecate OSGi events for Sling resource changes

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

Robert Munteanu resolved SLING-5169.
------------------------------------
    Resolution: Fixed

> Deprecate OSGi events for Sling resource changes
> ------------------------------------------------
>
>                 Key: SLING-5169
>                 URL: https://issues.apache.org/jira/browse/SLING-5169
>             Project: Sling
>          Issue Type: Sub-task
>          Components: API
>            Reporter: Tomek Rękawek
>            Assignee: Robert Munteanu
>             Fix For: API 2.10.0
>
>         Attachments: SLING-5169.patch
>
>
> With the new observation support (see parent SLING-4751) we'll have more robust way to get events regarding resource changes. Support for the old, OSGi-type events is provided by the {{OsgiObservationBridge}} service. We should deprecate the OSGi topic events {{SlingConstants.TOPIC_RESOURCE_*}}, so developers are aware about the new {{ResourceChangeListener}} service and will switch to it.



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