[ 
https://issues.apache.org/jira/browse/OAK-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

angela updated OAK-3358:
------------------------
    Component/s:     (was: security)

> Make SecurityProviderImpl independent from OSGi
> -----------------------------------------------
>
>                 Key: OAK-3358
>                 URL: https://issues.apache.org/jira/browse/OAK-3358
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Francesco Mari
>            Assignee: Francesco Mari
>
> This issue is a follow-up of OAK-3201. {{SecurityProviderImpl}} is currently 
> doing two different things. First, it is an implementation of 
> {{SecurityProvider}} that is supposed to be used outside of OSGi. Second, it 
> is an OSGi component capable of fetching its dependencies from the service 
> registry.
> I propose to split this two concerns in two different classes, and apply this 
> concept to both {{SecurityProviderImpl}} and its dependencies. I proposed a 
> patch in OAK-3201 outlining a possible solution. The comments in OAK-3201 
> provide more insights about the proposal.



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

Reply via email to