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 22:01:05 UTC
[jira] [Commented] (SLING-4929) Remove configuration logic from
SlingServerRepository
[ https://issues.apache.org/jira/browse/SLING-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658778#comment-14658778 ]
Carsten Ziegeler commented on SLING-4929:
-----------------------------------------
We should really avoid creating configurations within bundles. The repository implementation should be able to use default values without having a configuration with these values in config admin.
Creating configs in code is always problematic.
> 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
> 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)