You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Timothee Maret (JIRA)" <ji...@apache.org> on 2017/01/04 17:02:58 UTC
[jira] [Comment Edited] (SLING-4207) Add notifications upon tenant
changes
[ https://issues.apache.org/jira/browse/SLING-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798737#comment-15798737 ]
Timothee Maret edited comment on SLING-4207 at 1/4/17 5:02 PM:
---------------------------------------------------------------
Attaching a new patch which contains test coverage.
This patch is also available at https://github.com/tmaret/sling/commit/289a5b04df8141497e56389e9d621530b1471c89
was (Author: marett):
Attaching a new patch which contains test coverage
> 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
> Assignee: Felix Meschberger
> Fix For: Tenant 1.1.0
>
> Attachments: SLING-4207.patch, SLING-4207.patch, SLING-4207.patch, 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)