You could also use bnd's `@ServiceProvider` and/or `@ServiceConsumer`
annotations which handle all of this magic for you.
The addition of the service capability was recently added so is not
available until next release (5.0.0), but everything else is handled.
Before 5.0.0 this is what I
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="foo.bar.MySPI"
Ideally this could be automatically generated by tooling, when it sees the
Provide-Capability:
Hi guys,
is this the wrong list for such question?
Can you point me to a more suitable one?
Best regards,
Markus
Am Fr., 18. Okt. 2019 um 10:55 Uhr schrieb Markus Rathgeb :
>
> Hello,
>
> I have question about the serviceloader specific manifest entries (WRT
> to the example from
>
... not just DS, but OSGi CDI too with Bean Property Types [1]!
:)
[1]
https://osgi.org/specification/osgi.enterprise/7.0.0/service.cdi.html#service.cdi-bean.property.types
On Tue, Dec 17, 2019 at 7:03 AM David Leangen via osgi-dev <
osgi-dev@mail.osgi.org> wrote:
>
> Hi David,
>
> Ah, ok.
Hi David,
Ah, ok. Yes, that helps indeed. Thanks!
Cheers,
=David
> On Dec 17, 2019, at 19:55, David Bosschaert
> wrote:
>
> Hi David,
>
> This means that having an untyped map of configuration data is in most cases
> not what you want. More convenient is to convert it to a typed api.
Hi David,
This means that having an untyped map of configuration data is in most
cases not what you want. More convenient is to convert it to a typed api.
Using the OSGi converter to create an annotation instance is a very
convenient way to do this. Annotations are particularly useful since they
