sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marius Petria (JIRA)" <>
Subject [jira] [Commented] (SLING-3352) Expose OSGI configuration as JCR nodes
Date Wed, 05 Feb 2014 08:56:11 GMT


Marius Petria commented on SLING-3352:

[~fmeschbe], there are several proposals for exposing configuration as JCR nodes. I will try
to summarize them here:
1. fully synchronize certain configs in a designated location
2. have shadow nodes for those configs, i.e. syncronize only the creation and deletion and
resort to some other mechanisms for read and update 
3. do not create another copy but enhance the current JCR installer to put the copies it already
creates into a designated location for a certain factory

Can you please share your thoughts on these? Are we going in the right direction? Please have
in mind that while some solutions are proposed to be general the issue we are trying to solve
is particular to replication. We want to securely access through HTTP active configurations
of replication agents.

> Expose OSGI configuration as JCR nodes
> --------------------------------------
>                 Key: SLING-3352
>                 URL:
>             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
> 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
> - 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

View raw message