[OAK-3358] Make SecurityProviderImpl independent from OSGi

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Fix Version/s: 1.3.7, 1.4
• Component/s: core
• Assignee: Francesco Mari
• Reporter: Francesco Mari
• Created: 07/Sep/15 08:38
• Updated: 02/Mar/16 15:40
• Resolved: 18/Sep/15 07:43

Description

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.

Issue Links

• is related to: OAK-3201 Use static references in SecurityProviderImpl for composite services
• relates to: OAK-3346 Analyze the usages of AbstractServiceTracker