[ https://issues.apache.org/jira/browse/SLING-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886477#comment-13886477 ]
Carsten Ziegeler commented on SLING-3352: ----------------------------------------- I just would like to comment why we shouldn't use the sling:osgiconfig nodes used by the installer, these nodes are spread across the repository and might not reflect current state of the ConfigurationAdmin. These configurations might have been created through other providers of the installer (like the launchpad one or the file provider) or the installer wasn't running while a configuration has been changed etc. In addition, configuration nodes stored in the repo might be shadowed by others having higher precedence. So the only truth is the configuration admin. Or in short, the config nodes are not a 1:1 copy of the state in the configuration admin. > Expose OSGI configuration as JCR nodes > -------------------------------------- > > Key: SLING-3352 > URL: https://issues.apache.org/jira/browse/SLING-3352 > Project: Sling > Issue Type: Improvement > Reporter: Marius Petria > Labels: replication > > We need a safe way to expose OSGI configuration via HTTP. > Requirements: > - all configs for a certain factory should be manageable > - they should have associated JCR nodes that contain the config properties > - only configs that are available through ConfigurationAdmin should be > available > - the HTTP urls should have friendly names > - (Optional) the implementation should be general enough to be used for other > configs other than replication if needed > For example: a configuration with name publish for > org.apache.sling.replication.agent.impl.ReplicationAgentServiceFactory > should be mapped to /etc/replication/agent/publish > Problems with current implementation of JCR nodes created by JCR installed: > - Configuration files are read and created from /apps/.../config or > /libs/.../config, and there is no easy way to determine which are active in > the ConfigurationAdmin > - There is no way to restrict a repository path to create only configuration > from a specified factory (making it unusable with relaxed ACLs) > - The url of a configuration is unfriendly (it contains the fully qualified > name of the factory) > - The node types are not homogenous making it hard to use in a client > application (some are nt:file, some are sling:OsgiConfig) -- This message was sent by Atlassian JIRA (v6.1.5#6160)