I think cases where the service consumer doesn't need or want the
provider code (e.g. small or embedded environments) is one such
example. In such cases a separate API can keep things smaller and less
complicated on the consumer.
Scott
On 2/8/2018 12:54 PM, Peter Kriens via osgi-dev wrote:
I think there are only a few good cases where you really need an API bundle.
Virtually cases I’ve seen in the wild were incorrect because they fudged the
versions to make the API more backward compatible than it really was so more
providers could leverage it. In very few cases can you have
In my experience it is quite often handy to have a separate API bundle -
yours is one use case, another is where the system may run on different
platforms which require different implementations for some services (cloud
vs development machine, embedded vs dev, self-contained demo vs real
