[
https://issues.apache.org/jira/browse/SLING-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228365#comment-14228365
]
ASF GitHub Bot commented on SLING-4207:
---------------------------------------
GitHub user tmaret opened a pull request:
https://github.com/apache/sling/pull/50
SLING-4207 - Add notifications upon tenant changes
* Add API TenantConstants that defines the string constants to process the
events.
* Send events when tenant is added/removed or tenant properties are
set/removed from the implementation
* Increase minor package version
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tmaret/sling SLING-4184-events
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sling/pull/50.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #50
----
commit d1fe265d6446594f5fbc6890eebc810cbd6b055e
Author: tmaret <[email protected]>
Date: 2014-11-28T16:06:53Z
SLING-4207 - Add notifications upon tenant changes
* Add API TenantConstants that defines the string constants to process the
events.
* Send events when tenant is added/removed or tenant properties are
set/removed from the implementation
* Increase minor package version
----
> Add notifications upon tenant changes
> -------------------------------------
>
> Key: SLING-4207
> URL: https://issues.apache.org/jira/browse/SLING-4207
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Tenant 1.0.2
> Reporter: Timothee Maret
> Fix For: Tenant 1.0.4
>
> Attachments: SLING-4207.patch
>
>
> Currently, there is no clean way to detect when a tenant has been
> added/removed/modified.
> We may detect when a change is required by implementing the TenantCustomizer
> interface, however, it tells nothing about the actual completion of the
> change.
> We may listen for OSGI events under /etc/tenants but this requires the user
> to know where the tenants are located (which afaik, currently is not exposed).
> In order to allow apps reacting on tenant changes, I propose to either:
> I. extend the current SPI with an interface TenantEventListener that users
> can implement ; or
> II. send OSGI events form the current implementation.
> In both cases, the events should cover
> * Tenant added
> * Tenant removed
> * Property added
> * Property removed
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
