[
https://issues.apache.org/jira/browse/SLING-6263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15654654#comment-15654654
]
Oliver Lietz commented on SLING-6263:
-------------------------------------
bq. Before this change it was never executed at all
That is exactly the reason for my concerns... you could deploy them and be sure
they would not be executed until repository (re)start.
Therefore I had preferred a {{SlingRepositoryProcessor}} which is executed
whenever activated and a {{SlingRepositoryInitializer}} (only an empty marker
interface which extends {{SlingRepositoryProcessor}}, a copy of the existing
{{SlingRepositoryInitializer}}) which is only executed _before_ the repo is
started and in defined order (service ranking).
> Dependency problem between RepositoryInitializer and
> AbstractSlingRepositoryManager
> -----------------------------------------------------------------------------------
>
> Key: SLING-6263
> URL: https://issues.apache.org/jira/browse/SLING-6263
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Blocker
> Fix For: JCR Base 2.4.2
>
>
> As we can currently see on our Jenkins:
> https://builds.apache.org/job/sling-launchpad-builder-1.8/lastSuccessfulBuild/artifact/target/_-32861/sling/logs/error.log
> there is a dependency problem with the repository and repoinit.
> When the repository is started, there is no RepositoryInitializer
> service and the repository starts up fine. When the
> RepositoryInitializer arrives later it is completely ignored.
> I'm not 100% sure how to fix this, easiest fix would be to make a
> RepositoryInitializer required, but then this would mean only one of
> them is required.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
