ECF fully implements the latest versions of both the OSGi R6 Remote Services (1.0) and Remote Service Admin (1.1) specifications. Compliance with the specifications is tested daily by running the OSGi R6 Compatibility test suite as part of our continuous integration.

ECF also has a 'pluggable distribution provider' approach, and currently supports a variety of distribution providers including CXF, Jersey Jax-RS, Hazelcast, tcp, JMS, rosgi, websockets, and others [1].

We have a release coming up this week (3.13.0) [3] that among other things introduces a simplified API for creating distribution providers. All such providers will be automatically compliant with the OSGi R6 specifications, and of course may be done in open source or not using whatever transport is desired.

I am working on a tutorial for this new API as we speak, but for a preview here is the tutorial codebase [2].

Once it is fully in place, we will also be supporting the Aries distribution provider API Christian mentions.

We would very much like to have a Cellar-based distribution provider as well. Perhaps the simplified distribution provider API [2] will assist in making this happen.

Scott

[1] http://wiki.eclipse.org/Distribution_Providers
[2] https://github.com/ECF/ExampleRSADistributionProviders
[3] https://projects.eclipse.org/projects/rt.ecf/releases/3.13.0

On 3/15/2016 11:00 AM, Christian Schneider wrote:
CXF-DOSGi and cellar DOSGi are not related till now but they implement different specs anyway.
Cellar DOSGi implements the older and simpler Remote Services spec.

JB is planning to create a new Hazelcast transport for Aries RSA that then might replace Cellar DOSGi.

Christian

On 15.03.2016 17:39, Leschke, Scott wrote:
I'm curious what the relationship is between CXF DOSGi and Cellar DOSGi (feature:install cellar-dosgi)?

Scott

-----Original Message-----
From: Christian Schneider [mailto:cschneider...@gmail.com] On Behalf Of Christian Schneider
Sent: Tuesday, March 15, 2016 11:05 AM
To: user@karaf.apache.org
Subject: Re: CXF Dosgi

The service worked fine for me:
feature:repo-add cxf-dosgi 1.7.0
feature:install cxf-dosgi-discovery-distributed cxf-dosgi-zookeeper-server install -s mvn:es.yaroki/service

Log shows:
2016-03-15 17:03:08,157 | INFO  | er])-EventThread |
PublishingEndpointListener       | 53 -
cxf-dosgi-ri-discovery-distributed - 1.7.0 | Local EndpointDescription
added: {endpoint.framework.uuid=8ed1316c-e222-4e37-8135-69be5c92f3f8,
endpoint.id=http://172.20.0.187:8181/cxf/ILblService,
endpoint.package.version.es.yaroki.service=0.0.1,
endpoint.service.id=112, objectClass=[es.yaroki.service.MyService],
org.apache.cxf.ws.address=http://172.20.0.187:8181/cxf/ILblService,
osgi.service.blueprint.compname=serviceBean, service.bundleid=52, service.imported=true, service.imported.configs=[org.apache.cxf.ws],
service.intents=[SOAP.1_1, HTTP, SOAP], service.scope=bundle}

and the service is available.

Christian


On 15.03.2016 16:45, conejo wrote:
Try this:

https://github.com/LuisLozano/dosgi



--
View this message in context:
http://karaf.922171.n3.nabble.com/CXF-Dosgi-tp4045786p4045793.html
Sent from the Karaf - User mailing list archive at Nabble.com.

--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com




Reply via email to