This is an automated email from the ASF dual-hosted git repository.
kwin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/master by this push:
new bfce4a2 clarify how resource observation works with respect to
cluster repositories
bfce4a2 is described below
commit bfce4a2253d570ed433e64ad571b26925eae1945
Author: Konrad Windszus <k...@apache.org>
AuthorDate: Thu Oct 12 13:43:47 2017 +0200
clarify how resource observation works with respect to cluster
repositories
---
src/main/jbake/content/documentation/the-sling-engine/resources.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/src/main/jbake/content/documentation/the-sling-engine/resources.md
b/src/main/jbake/content/documentation/the-sling-engine/resources.md
index cd2511a..13c3c41 100644
--- a/src/main/jbake/content/documentation/the-sling-engine/resources.md
+++ b/src/main/jbake/content/documentation/the-sling-engine/resources.md
@@ -159,11 +159,12 @@ To be notified whenever certain resources or their
properties have been modified
*This API is only available since Sling API 2.11.0
([SLING-4751](https://issues.apache.org/jira/browse/SLING-4751)).*
-Register an OSGi service for
[`org.apache.sling.api.resource.observation.ResourceChangeListener`][6] or
[`org.apache.sling.api.resource.observation.ExternalResourceChangeListener`][7]
to be notified about changes. Certain properties can be used to restrict
subscription to only a subset of events.
+Register an OSGi service for
[`org.apache.sling.api.resource.observation.ResourceChangeListener`][6] to be
notified about local changes. To be also notified about external changes (i.e.
changes triggered by another Sling instance leveraging a clustered repository
make sure that your service implementation also implements the marker interface
[`org.apache.sling.api.resource.observation.ExternalResourceChangeListener`][7].
The interface `ExternalResourceChangeListener` is not supposed to [...]
+Certain properties can be used to restrict subscription to only a subset of
events.
### OSGi Event Admin
-Resource events are sent out via the OSGi Event Admin. You can subscribe to
those event by registering an OSGi service for
[`org.osgi.service.event.EventHandler`][8]. Several properties should be used
to restrict the subscription to only the relevant event. The event topics which
are used for resources are listed as constants in
[`org.apache.sling.api.SlingConstants`][9] starting with the prefix `TOPIC_`.
+Resource events are sent out via the OSGi Event Admin. You can subscribe to
those event by registering an OSGi service for
[`org.osgi.service.event.EventHandler`][8]. Several properties should be used
to restrict the subscription to only the relevant event. The event topics which
are used for resources are listed as constants in
[`org.apache.sling.api.SlingConstants`][9] starting with the prefix `TOPIC_`.
You receive events no matter whether they originate from the local repository
or fr [...]
## Wrap/Decorate Resources
--
To stop receiving notification emails like this one, please contact
['"commits@sling.apache.org" <commits@sling.apache.org>'].
