Hi Markus, Sorry for the late reply.
I think it makes sense in the bundle_provider to also have the capability Provide-Capability: osgi.service;objectClass:List<String>="foo.bar.MySPI" Ideally this could be automatically generated by tooling, when it sees the Provide-Capability: osgi.serviceloader;osgi.serviceloader=... capability, but I don't think this auto-generation happens right now. > Or should the requirement > > osgi.service;filter:="(objectClass=foo.bar.MySPI)";effective:=active > > also be satisfied by the provided > > osgi.serviceloader;osgi.serviceloader=foo.bar.MySPI > > (and its requirement for the Registrar) by the resolving implementations? > I don't think that during resolution such 'complicated' mapping should take place. Capabilities and requirements are straightforward so an osgi.service requirement should be satisfied by an osgi.service capability, not a capability in some other namespace. But yes, providing the additional osgi.service capability in the bundle_provider makes sense to me. Best regards, David
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
