[jira] [Resolved] (SLING-5456) Implement SlingRepositoryInitializer plug-ins to setup the repository

["Bertrand Delacretaz (JIRA)" <ji...@apache.org>]

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

Bertrand Delacretaz resolved SLING-5456.
----------------------------------------
    Resolution: Fixed

Implemented in http://svn.apache.org/r1727312 , with tests

> Implement SlingRepositoryInitializer plug-ins to setup the repository
> ---------------------------------------------------------------------
>
>                 Key: SLING-5456
>                 URL: https://issues.apache.org/jira/browse/SLING-5456
>             Project: Sling
>          Issue Type: New Feature
>          Components: JCR
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>             Fix For: JCR Base 2.3.2, JCR API 2.3.2
>
>
> I'd like to implement a {{SlingRepositoryInitializer}} extension point for use cases like setting up service users and ACLs and creating the "base tree" of content as described in SLING-5449. 
> This can also be very useful to handle content migrations or other cleanup operations in upgrades.
> The scenario is that before registering the {{SlingRepository}} service, all active {{SlingRepositoryInitializer}} services are called in order of their service ranking, passing them the upcoming {{SlingRepository}} service so that they can act on it. Any exception thrown in this processing causes the {{SlingRepository}} service registration to be canceled.
> The {{SlingRepositoryInitializer}} javadocs must stress that those services need to take clustered scenarios into account, and if necessary implement locking mechanisms to avoid stepping on each other's toes.



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