[ 
https://issues.apache.org/jira/browse/SLING-5872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385464#comment-15385464
 ] 

ASF GitHub Bot commented on SLING-5872:
---------------------------------------

GitHub user tmaret opened a pull request:

    https://github.com/apache/sling/pull/154

    SLING-5872 - Management of agent configurations must identify 
configurations by name

    * Remove the agents with the same name wich are not bind to the same factory

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tmaret/sling SLING-5872

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/sling/pull/154.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #154
    
----
commit d24ef381afdc4d4c93378694772c9afe53e45ba9
Author: tmaret <[email protected]>
Date:   2016-07-20T07:02:52Z

    SLING-5872 - Management of agent configurations must identify 
configurations by name
    
    * Remove the agents with the same name wich are not bind to the same factory

----


> Management of agent configurations must identify configurations by name 
> ------------------------------------------------------------------------
>
>                 Key: SLING-5872
>                 URL: https://issues.apache.org/jira/browse/SLING-5872
>             Project: Sling
>          Issue Type: Bug
>          Components: Distribution
>    Affects Versions: Content Distribution Core 0.1.18
>            Reporter: Timothee Maret
>            Assignee: Timothee Maret
>
> Currently, the configurations are identified by the tuple {{(name,kind)}}.
> As a consequence, it is possible to create two configurations with the same 
> name but different kind, using the Sling POST servlet on path
> {code}
> /libs/sling/distribution/settings/agents/<agentName>
> {code}
> This breaks the concept of having a single resource type (and thus a single 
> agent) for a given type.
> This is somewhat related to SLING-5742, however it does not cover creation of 
> agents via the OSGI consoles (only via the Sling POST servlet).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to