Hi Carsten.
Sorry to answer a bit late but I needed to check if my subsystems
knowledge was still updated ;)
Your solution to install the bundle in every scoped subsystem would be
good, if Subsystems impl allowed this.
But its not the case, the Subsystems doesn't allows to have more than
one bundle using same name/version inside the container, even if it is
being provided as a constituent of a scope subsystem.
In order to test I've created a composite subsystem and included as a
constituent the bundle:"org.apache.felix.bundlerepository". This bundle
is required in order aries subsystem to boot. When I tried to install
this subsystem, I got this exception:
org.osgi.service.subsystem.SubsystemException:
org.osgi.framework.BundleException: A bundle is already installed with
the name "org.apache.felix.bundlerepository" and version "2.0.10"
But I think that this theme about how specs that provides Extenders (as
DS/SCR and Configurator specs) should implement in order to support
scoped subsystems should be in the compendium...
best regards,
Cristiano
On 09/08/2018 04:28, Carsten Ziegeler wrote:
The configurator does not have such a setting, it uses it's own bundle
context to find other bundles. Therefore if you want to use it with
scoped subsystems, the best is to simply install it in every scoped
system. It will pick up the configuration admin using the bundle
containing the configuration
Regards
Carsten
Cristiano Gavião wrote
Hi all,
Felix SCR has a property named "ds.global.extender" that instructs SCR
to use the System Bundle's bundleContext instead its own bundleContext
in order to register its extender service.
It is useful to listening for bundles that are installed inside scoped
subsystems.
thanks,
Cristiano
