[jira] [Commented] (SLING-3578) [loginservice] serviceusermapper merged configuration

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

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

Carsten Ziegeler commented on SLING-3578:
-----------------------------------------

I think the easiest way is to use a combination of OSGi configuration and factory configurations:
* Central configuration is in the PID=org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl configuration
* Deployed application may provide ammendments as configurations with factory.PID=org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.ammended 

The service user mapper would merge the ammended configuration into the central configuration, where central configuration overwrites settings in the ammended configuration. Other than that there is no guaranteed ordering of configurations. If there are mulitple factory configurations for the same mapping, this should at least  log an error.
If a factory config and a global config overlap this should be log as a warning or info

> [loginservice] serviceusermapper merged configuration
> -----------------------------------------------------
>
>                 Key: SLING-3578
>                 URL: https://issues.apache.org/jira/browse/SLING-3578
>             Project: Sling
>          Issue Type: Improvement
>          Components: Service User Mapper
>            Reporter: Antonio Sanso
>            Assignee: Carsten Ziegeler
>            Priority: Minor
>             Fix For: Service User Mapper 1.0.2
>
>
> It would be nice to have a way to support an application deployment providing some service user mapping configuration to ammend/merge the existing configuration.  
> See also discussion in [0]
> [0] http://sling.markmail.org/thread/nxs4dqqiejvvkcx2



--
This message was sent by Atlassian JIRA
(v6.2#6252)