[jira] [Updated] (SLING-3828) Hardcoded creation of SegmentNodeStoreService config makes it impossible to remove this configuration
[ https://issues.apache.org/jira/browse/SLING-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-3828: Fix Version/s: JCR Oak Server 1.0.0 Launchpad Builder 7 Hardcoded creation of SegmentNodeStoreService config makes it impossible to remove this configuration - Key: SLING-3828 URL: https://issues.apache.org/jira/browse/SLING-3828 Project: Sling Issue Type: Bug Components: Oak Reporter: David Bosschaert Fix For: Launchpad Builder 7, JCR Oak Server 1.0.0 Attachments: oak-server.diff The Activator in org.apache.sling.jcr.oak.server always creates a configuration item with PID org.apache.jackrabbit.oak.plugins.segment.SegmentNodeStoreService if it isn't there. This means that if you delete this configuration, it will reappear on restart. In some cases this configuration is undesirable, for example when running with Mongo. Therefore it should be possible to delete it. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3828) Hardcoded creation of SegmentNodeStoreService config makes it impossible to remove this configuration
[ https://issues.apache.org/jira/browse/SLING-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert updated SLING-3828: Attachment: oak-server.diff The attached patch replaces the config generation in the Activator with a configuration provided via the launchpad. The configuration will still appear by default, but when deleted it will not reappear on restart. Hardcoded creation of SegmentNodeStoreService config makes it impossible to remove this configuration - Key: SLING-3828 URL: https://issues.apache.org/jira/browse/SLING-3828 Project: Sling Issue Type: Bug Components: Oak Reporter: David Bosschaert Attachments: oak-server.diff The Activator in org.apache.sling.jcr.oak.server always creates a configuration item with PID org.apache.jackrabbit.oak.plugins.segment.SegmentNodeStoreService if it isn't there. This means that if you delete this configuration, it will reappear on restart. In some cases this configuration is undesirable, for example when running with Mongo. Therefore it should be possible to delete it. -- This message was sent by Atlassian JIRA (v6.2#6252)
