> On 10 Nov 2016, at 16:07, Christian Schneider <ch...@die-schneider.net> wrote: > > Hi Neil, > > that sounds very good. I was not aware of the Endpoint publishing. I will > test the interoperability as soon as I can. > I will also look into making CXF-DOSGi implement the spec as well as possible > so we get away a bit from the proprietary configs.
FWIW the implementation from Liferay doesn’t yet have this functionality — it’s a work in progress. So I wasn’t able to demo this aspect when I talked at OSGiCE. Also this is only an RFC at present so it’s not guaranteed to make it into the final spec in the current form. I’m not sure if you or your company are OSGi Alliance members but if you are then it would be a good idea to get involved with the spec discussions. Neil > > Anyway it is really good that we also get a jersey based JAX-RS impl in Aries > as quite a few people are asking for this. > > Christian > > On 10.11.2016 16:40, Neil Bartlett wrote: >> Christian, have you read the RFC for the JAX-RS whiteboard? It already does >> exactly this. >> >> When the whiteboard picks up a REST service, it publishes an Endpoint >> service to the service registry, which has service.exported.interfaces=* and >> a URL property defined. If you have an RSA provider installed then this will >> be picked up and advertised to the network in the normal way. >> >> At the client end, you can define a reference to the Endpoint service and >> thereby obtain the URL property. Thence a standard HTTP or REST client >> library can be used to connect to the REST server. >> >> Neil > > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > http://www.talend.com > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
