[jira] [Resolved] (SLING-3352) Expose OSGI configuration via HTTP

["Tommaso Teofili (JIRA)" <ji...@apache.org>]

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

Tommaso Teofili resolved SLING-3352.
------------------------------------

    Resolution: Fixed
      Assignee: Tommaso Teofili  (was: Carsten Ziegeler)

I've applied Marius's patch at r1578436, thanks Marius for your contribution(s)

> Expose OSGI configuration via HTTP
> ----------------------------------
>
>                 Key: SLING-3352
>                 URL: https://issues.apache.org/jira/browse/SLING-3352
>             Project: Sling
>          Issue Type: Improvement
>            Reporter: Marius Petria
>            Assignee: Tommaso Teofili
>              Labels: replication
>         Attachments: SLING-3352.1.patch, SLING-3352.2.patch, SLING-3352.3.patch, SLING-3352.4.patch, SLING-3352.patch
>
>
> 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.2#6252)