You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Timothee Maret (JIRA)" <ji...@apache.org> on 2017/02/07 15:57:41 UTC
[jira] [Updated] (SLING-6434) serviceName configurations must be
considered null when empty/blank
[ https://issues.apache.org/jira/browse/SLING-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothee Maret updated SLING-6434:
----------------------------------
Fix Version/s: (was: Content Distribution Core 0.1.20)
Content Distribution Core 0.2.0
> serviceName configurations must be considered null when empty/blank
> -------------------------------------------------------------------
>
> Key: SLING-6434
> URL: https://issues.apache.org/jira/browse/SLING-6434
> Project: Sling
> Issue Type: Bug
> Components: Content Distribution
> Affects Versions: Content Distribution Core 0.1.16
> Reporter: Timothee Maret
> Assignee: Timothee Maret
> Fix For: Content Distribution Core 0.2.0
>
>
> Currently, serviceName is an OSGI property that can be set on most SCD services in order to specify the id of the user accessing the repository.
> This configuration is optional (default is to use the service user).
> Empty/blank configurations should be considered as not configured.
> Indeed, empty/blank configurations are faced whenever configuring an empty configuration using the Felix console.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)