You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Francesco Mari (JIRA)" <ji...@apache.org> on 2015/09/07 10:38:45 UTC

[jira] [Created] (OAK-3358) Make {{SecurityProviderImpl}} independent from OSGi

Francesco Mari created OAK-3358:
-----------------------------------

             Summary: Make {{SecurityProviderImpl}} independent from OSGi
                 Key: OAK-3358
                 URL: https://issues.apache.org/jira/browse/OAK-3358
             Project: Jackrabbit Oak
          Issue Type: Bug
          Components: core, security
            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)