[
https://issues.apache.org/jira/browse/SLING-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13869625#comment-13869625
]
Marius Petria edited comment on SLING-3315 at 1/13/14 3:55 PM:
---------------------------------------------------------------
Hi Bertrand,
The proposed patch only refactors the exiting HTTP API that is basically a
wrapper of ConfigurationAdmin. One needs a HTTP endpoint for configuration in
order to build custom management ui for replication.
You are suggesting that we should drop this custom HTTP wrapper and use the
default SlingPostServlet to administer the configs, right? Or are you thinking
about configuring via /system/console/configMgr?
UPDATE: To answer your question the replication is configured primarily using
OSGI configs and the HTTP API is just a wrapper.
Marius
was (Author: mpetria):
Hi Bertrand,
The proposed patch only refactors the exiting HTTP API that is basically a
wrapper of ConfigurationAdmin. One needs a HTTP endpoint for configuration in
order to build custom management ui for replication.
You are suggesting that we should drop this custom HTTP wrapper and use the
default SlingPostServlet to administer the configs, right? Or are you thinking
about configuring via /system/console/configMgr?
Marius
> Refactor replication HTTP API
> -----------------------------
>
> Key: SLING-3315
> URL: https://issues.apache.org/jira/browse/SLING-3315
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: Marius Petria
> Labels: replication
> Attachments: SLING-3315.patch
>
>
> Refactor HTTP API in order to access independently the configuration of an
> agent and the service API for an agent. This was needed because there are
> times when a configuration can exist without an agent being available (e.g.
> when the agent is not disabled).
> Proposed API:
> Managing configuration
> POST /system/replication/config/agent (creates and agent cofig)
> GET /system/replication/config/agent (retrieves all agents config)
> POST /system/replication/config/agent/{agentName} (updates and agent)
> GET /system/replication/config/agent/{agentName} (retrieves the agent
> config)
> DELETE /system/replication/config/agent/{agentName} (deletes an agent config)
> Managing agent
> POST /system/replication/config/agent/{agentName} (schedules a package
> for replication or removes one from the queue)
> GET /system/replication/config/agent/{agentName}/queue (lists the
> packages in the queue)
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
