I think such attempts, in the past, have been fraught with failure. The primary reason, I surmise, is that River requires code downloading (and thus, a very different classloading scheme).
I myself can foresee a very elegant marriage between the two technologies, where downloaded code is automatically installed as bundles in the OSGi runtime (and perhaps automatically removed, if necessary), but there are probably many subtle complexities. As a strong, production-time user of both technologies, I would absolutely love to see progress in making the two play together. How do you propose we move forward? regards, Dawid Loubser On 27/09/2014 11:12, bill pickup wrote: > > Greetings. > > OSGi, > being service driven, and thus a nontoo-distant cousin to > Jini/River, needs an extender to talk to same, methinks. Has anyone > in the community had fun in this department? > > Bill >
