[
https://issues.apache.org/jira/browse/SLING-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659649#comment-14659649
]
Robert Munteanu commented on SLING-4929:
----------------------------------------
OK so in that case we should
- remove the code that creates configurations fromt the bundle's Activator
- remove ConfigurationPolicy.REQUIRE from the SlingServerRepository
- adapt the SlingServerRepository to work with default values if no
configuration is present
I'll try to have a look this week
> Remove configuration logic from SlingServerRepository
> -----------------------------------------------------
>
> Key: SLING-4929
> URL: https://issues.apache.org/jira/browse/SLING-4929
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Reporter: Robert Munteanu
> Fix For: JCR Jackrabbit Server 2.3.0
>
>
> The bundle's {{Activator}} creates a default configuration if none if found,
> to ensure that there is a configuration available for the
> {{SlingServerRepository}}. The {{Activator}} also handles the creation of the
> home directory of the repository and of the default configuration file.
> When using a configuration from the provisioning model, the repository home
> and the config file are not created, therefore the repository startup fails.
> The solution is to handle the directory creation and the configuration file
> initialisation directly in the {{SlingServerRepository}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
