Arnoud Glimmerveen created FELIX-6355:
-----------------------------------------
Summary: Bundle with plain osgi.extender requirement triggers 'No
configuration found' error
Key: FELIX-6355
URL: https://issues.apache.org/jira/browse/FELIX-6355
Project: Felix
Issue Type: Bug
Components: Configurator
Reporter: Arnoud Glimmerveen
When a bundle declares a requirement on the {{osgi.extender}} namespace without
a filter, it can trigger an error from the configurator:
{noformat}
[ERROR] No configurations found at path OSGI-INF/configurator
{noformat}
Apparently the configurator assumes that if a bundle has a requirement on the
{{osgi.extender}} namespace *and* the requirement is wired to the configurator
bundle, it must be that the bundle holds configuration that needs to be
processed. Which is a correct assumption when the {{osgi.extender}} namespace
is properly used, but in the above described situation can fail.
To safe-guard against, the configurator could do a sanity check when evaluating
the wirings to see if the related requirement filters on
{{(osgi.extender=osgi.configurator)}}.
Unrelated to this specific case, it would be helpful if the 'No configurations
found' error would mention the bundle involved.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
