sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothee Maret (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SLING-6434) serviceName configurations must be considered null when empty/blank
Date Wed, 04 Jan 2017 14:46:58 GMT

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

Timothee Maret updated SLING-6434:
----------------------------------
    Affects Version/s: Content Distribution Core 0.1.16

> 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: Distribution
>    Affects Versions: Content Distribution Core 0.1.16
>            Reporter: Timothee Maret
>            Assignee: Timothee Maret
>
> 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.4#6332)

Mime
View raw message