On 5/23/2016 8:17 AM, Peter Kriens wrote:
On 23 mei 2016, at 16:27, Arjun Panday <[email protected]
<mailto:[email protected]>> wrote:
With OSGi, you have to be "all in" ;
... like OSGi minus Classloading.
But what’s left of OSGi without classloading?
Actually a surprising amount of functionality :-) Karl Pauls (who did
PojoSR which I think is the parent of OSGi connect at Apache?) showed
you can use DS perfectly on this model along with many standard
implementations.
My understanding is also that PojoSR led to Apache Connect.
Inspired by Connect, I've created a small and open service registry
API: a thin factory interface for starting, configuring, and accessing
a service registry from java. This API can have multiple
implementations...one of which is currently provided by Apache connect
[1]. It uses java's ServiceLoader to create, initialize, and access a
serviceRegistry instance. There are also some early example projects
that use DS, Remote Service Admin/Remote Services, ServiceTracker,
LogService, osgi console, and event admin.
The things you lack are bundle uninstall, private code, Bundle
classpath, and a large number of protections. Bundle install, start,
stop, and the complete service layer all work fine.
Yes, indeed.
Scott
[1] https://github.com/ECF/ServiceRegistry
[2]
https://github.com/ECF/ServiceRegistry/blob/master/projects/examples/mycorp.examples.timeservice.sr.host/src/mycorp/examples/timeservice/sr/host/Main.java
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
