[
https://issues.apache.org/jira/browse/SLING-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814764#comment-13814764
]
Tommaso Teofili commented on SLING-3223:
----------------------------------------
bq. HTTP POST (/w parameters) to
http://host:port/system/replication/agent/configuration/foo for updating
configuration of agent foo
typo there, sorry, it's :
{code}
HTTP POST (/w parameters) to
http://host:port/system/replication/agent/foo/configuration for updating
configuration of agent foo
{code}
bq. Makes me think you're using your own configuration mechanism instead of
using OSGi configs, as Toby also notes. Is there a reason for that? Otherwise,
using OSGi configs should allow you to get rid of some code, and reuse the
standard webconsole and other tools to manage configs.
I'm using OSGi configs (configuration factory /w sling:OsgiConfig nodes) for
creating configurations then for retrieving / updating configurations I use a
resource provider which maps the HTTP request to the resource
{code}
/system/replication/agent/foo/configuration
{code}
first to the agent /system/replication/agent/foo then I use ConfigurationAdmin
to get the OSGi config for that agent.
Maybe (probably, at this point :) ) I'm not aware of simpler existing mechanism
for retrieving / updating OSGi configurations so a pointer there would be good.
bq. But all this can be handled once your code is donated, IMO it doesn't
prevent us from committing your code once the paperwork is ok.
good
> Donation of a replication module for Sling
> ------------------------------------------
>
> Key: SLING-3223
> URL: https://issues.apache.org/jira/browse/SLING-3223
> Project: Sling
> Issue Type: Task
> Components: Extensions
> Reporter: Tommaso Teofili
> Attachments: SLING-3223.patch
>
>
> Issue to track donation of a replication module for Sling, see thread at
> http://markmail.org/thread/ic62k5pc34ppb5ko
--
This message was sent by Atlassian JIRA
(v6.1#6144)
