[
https://issues.apache.org/jira/browse/SLING-5162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960717#comment-14960717
]
Carsten Ziegeler commented on SLING-5162:
-----------------------------------------
Yes, right, we can't simply remove the OSGi bridge, therefore deprecating the
TOPIC_RESOURCE_* constants in the API is a good step.
We can also add a switch to disable the bridge.
I have some other concern about observation/eventing in general and will bring
that to the list next week
> 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)
