[
https://issues.apache.org/jira/browse/FELIX-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks updated FELIX-4467:
--------------------------------
Fix Version/s: scr-2.0.0
> Option to use system bundle context for tracking bundles
> --------------------------------------------------------
>
> Key: FELIX-4467
> URL: https://issues.apache.org/jira/browse/FELIX-4467
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Reporter: Thomas Watson
> Assignee: David Jencks
> Fix For: scr-2.0.0
>
>
> My understanding is that the SCR implementation bundle uses its own bundle
> context to track bundles that contain service components. A majority of the
> time this is the correct thing to do.
> In environments that use an isolation engine there may be scenarios where the
> SCR bundle context does not have visibility to all the bundles it should be
> extending. For example, OSGi Subsystems or Equinox regions. In such
> scenarios it may be desirable to install a single implementation of SCR which
> has the ability to extend all bundles installed in the framework regardless
> of what subsystem or region the extendee bundle is installed.
> One way to accomplish this is to use the system bundle context to track
> bundle to extend. SCR still needs to use the extendee context in order
> interact with the service registry on behalf of the extendee bundle (e.g.
> listen for service registrations, get services etc.).
> If we do this there should probably be an option to enable using the
> system.bundle context and the default behavior is to still use the context of
> the SCR bundle
--
This message was sent by Atlassian JIRA
(v6.2#6252)
