You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/08/05 18:33:05 UTC

[jira] [Reopened] (SLING-4927) Unable to configure the SlingServerRepository using the provisioning model

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

Carsten Ziegeler reopened SLING-4927:
-------------------------------------

We should not create a configuration if one is missing. The implementation should work without a configuration in configuration admin and revert to default values. So instead of requring the configuration, it should be optional.
Creating configurations in code is imho not a good practice

> Unable to configure the SlingServerRepository using the provisioning model
> --------------------------------------------------------------------------
>
>                 Key: SLING-4927
>                 URL: https://issues.apache.org/jira/browse/SLING-4927
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Robert Munteanu
>            Assignee: 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)