Karl Pauls created SLING-10494:
----------------------------------
Summary: Configuration API should have a way to allow empty
configurations
Key: SLING-10494
URL: https://issues.apache.org/jira/browse/SLING-10494
Project: Sling
Issue Type: Improvement
Components: Feature Model
Affects Versions: Feature Model API Regions Extension 1.3.0
Reporter: Karl Pauls
Assignee: Carsten Ziegeler
Fix For: Feature Model API Regions Extension 1.3.2
The way the Configuration API currently handles configurations (and factory
configurations) is that an empty entry means don't allow. In other words,
listing an empty configuration (factory) is the same as marking it as
internal-configuration(-factory).
That makes sense in as far as that makes it nicer to be able to specify
configurations that are not allowed inline with the other configurations -
however, it misses a case where it is now impossible to allow an empty
configuration.
That could be problematic as sometimes, empty configurations are used to
configure e.g. services - that use case would at a minimum now not show up in
the Configuration API as one would be forced not to mention the configuration
at all in order to allow somebody to still be able to create an empty
configuration.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
