I also experimented with Felix connect a bit today. It seems to work
quite fine. I was able to run karaf decanter bundles using Connect
without changing any code.
The decanter bundles also use DS so this also works fine by simply also
loading the scr bundle.
When looking into the connect ServiceRegistry interface I have the
impression that it is highly redundant.
Basically all it offers is also available from the BundleContext of the
FrameWork bundle (0).
So I think the only thing we need to standardize is how to bootstrap
connect.
I am pretty sure we can already do this with the OSGi FrameworkFactory.
|FrameworkFactory frameworkFactory = ServiceLoader.load(
FrameworkFactory.class).iterator().next(); ||Framework framework = frameworkFactory.newFramework(config);
framework.start();|
WDYT?
Christian
On 24.05.2016 20:25, Scott Lewis wrote:
On 5/24/2016 11:20 AM, Scott Lewis wrote:
All I've done so far is to include previously-built bundles/jars on
the Connect classpath (using the classpath bundle finder) on startup,
and used DS to register and export a remote service [1], and discover
and then dynamically inject remote service proxy into consumer (in
jar) [2].
Oops
[1]
https://github.com/ECF/ServiceRegistry/tree/master/projects/examples/com.mycorp.examples.timeservice.sr.host
[2]
https://github.com/ECF/ServiceRegistry/tree/master/projects/examples/com.mycorp.examples.timeservice.sr.consumer.ds
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
