Hi Scott, first of all thank you for the pointer to RSA and D-OSGi. I've alread worked in the past with that (the CXF implementation mainly though).
However, architecturally speaking, I have a situation like this: ReST --> (X) --> DataService ...where (X) is the routing piece that I want to implement generically, so that it looks to the ReST-layer like this: ReST --> DataService One of the points here is that the initial ReST layer may just be one kind of presentation. E.g. a JMX integration and Karaf Commands may follow. And I don't want to code he decision logic three times or even more. So all this should be run inside the same JVM/OSGi framework instance and with as little runtime overhead as possible. Thanx anyway, Ancoron On 01/01/2015 06:39 PM, Scott Lewis wrote: > On 1/1/2015 8:47 AM, Peter Kriens wrote: >> Huh? This is a perfect example of the OSGi service model. Why on earth >> would you drag in RSA? Of course RSA is lovely when you ant to run >> your backend handler on another OSGi framework but RSA/Distributed >> OSGi seems to be as orthogonal as you can get to the original >> question? Or am I missing something? > > Yeah, I think you are missing something. > > As you say, he appears to want to expose a REST service as an OSGi > service. Remote Service proxies are OSGi services too, even if they > have no OGSi backend handler at all...e.g. [3]. > > Of course you are right that RSA is lovely when you have OSGi RS on > 'both sides', but my point is it can also be lovely when used for just > the proxy/consumer side. > > Scott > > > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
