Correct. I applied Gregg's patch to our private branch of River 11 months ago and we've been using it successfully under Equinox since then.
I had to make one very big hack for backward compatibility to Jini 2.1, though. In the client code, I have an URLStreamHandlerFactory that checks for "reggie-dl.jar" and if it's version number is missing or too old, then it replaces it on the fly with a new one bundled with the client. I had to do that because the old reggie-dl.jar classes (I'm having trouble remembering which -- maybe ServiceTypeBase?) did not work under OSGi without a change. Chris -----Original Message----- From: Peter Firmstone [mailto:[email protected]] Sent: Monday, August 29, 2011 2:49 AM To: [email protected] Subject: Re: Usability - "The Platform" > Peter, et al, > > Would the OSGi services specs provide a good foundation for defining a > platform? The specs include Remote Services Administration (RSA). OSGi > technology solves or mitigates classpath issues. Admittedly, I don't know > how or if the RSA spec addresses codebase issues. > > The proliferation of OSGi technology is pretty substantial. Intuitively, > OSGi technology and River seem complementary. I mentioned OSGi technology > and River a year or so go, so I apologize if I'm beating a dead horse. When merge Gregg's CodebaseAccessClassLoader back into the main trunk... Chris found this enabled him to utilise OSGi. Cheers, Peter.
