Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-dev] How to document OSGi extensibility?

OSGi is making use of annotations in several places to make development easier. DS annotations are a good example.

With R7 the bundle annotations were added

https://blog.osgi.org/2018/07/osgi-r7-highlights-bundle-annotations.html?m=1

And there are also component property type annotations that translate to service properties for example. And it is a good practice to even define such annotations. Unfortunately PDE does not support DS 1.4.

In my recent blog post about jax-rs whiteboard I show two use cases for bundle annotations. The package export definition and the requirement of the Configurator. If that is of any help to get an understanding. 

Mickael Istria <mistria@xxxxxxxxxx> schrieb am Fr., 22. Jan. 2021, 16:23:


On Fri, Jan 22, 2021 at 4:05 PM Christoph Läubrich <laeubi@xxxxxxxxxxxxxx> wrote:
OSGi already defines some annotations for the package level see , OSGi
DS makes heavy use with great success of annotations.

OK, can you please share a link to such example of package-info that's the good OSGi way. Maybe we can just mimic that and be done with it. 

The problem is more that the Eclipse way of thinking is sometimes
incompatible with standard OSGi ;-)

I think it's more that Eclipse Platform developers are not really top OSGi experts. They're using OSGi here and there as it fits, but Eclipse still has an extension registry and many other things that -despite some technical limitations- do work very well in most cases and that make people still rely on them without having to leverage OSGi much.
And this Whiteboard annotation isn't standard OSGi (yet?)

But I think if a draft for a @Whiteboard annotation could be provided in
Eclipse it might become the reference-implementation of an official
Eclipse specification later on :-)
[1] https://blog.osgi.org/2018/07/osgi-r7-highlights-bundle-annotations.html

To be clear, Eclipse Platform is not an incubator of OSGi, it's placed downstream of OSGi and leverages what is released.
So while Eclipse Platform code can be used as example (in some WIP/Drafts Gerrit patch) to help with design of such annotation for OSGi, the project doesn't aim at being a reference implementation to host such experimentation and won't merge experimental code.
That said, Equinox may be interesting in hosting such development. It's more a topic to bring on the equinox-dev@xxxxxxxxxxx mailing-list; which I believe has more interaction with the OSGi Working Group so such development likely to be more successful there.
_______________________________________________
platform-dev mailing list
platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev

Back to the top