Re: [osgi-dev] CFA: Assistance requested to produce LWJGL OSGi bundles

On 2017-02-21T10:30:16 -0500 Raymond Auge wrote: > I'm sorry I wasn't able to help solving your problems. > > However I wanted to say this is a very nice improvement. I had done some > light LWJGL & OSGi work a few years ago and this change should greatly > improve

Re: [osgi-dev] CFA: Assistance requested to produce LWJGL OSGi bundles

I'm sorry I wasn't able to help solving your problems. However I wanted to say this is a very nice improvement. I had done some light LWJGL & OSGi work a few years ago and this change should greatly improve this type of project! Kudos! and ... Let the games begin! ;) - Ray On Tue, Feb 21, 2017

Re: [osgi-dev] CFA: Assistance requested to produce LWJGL OSGi bundles

On 2017-02-14T13:01:01 + list+org.o...@io7m.com wrote: > Hello! > > I'm currently in the process of repackaging the LWJGL [0] jar files > as OSGi bundles [1] with some welcome assistance from the author. We eventually got all of the issues solved, and the next release of LWJGL should now be

Re: [osgi-dev] Question about class loaders

this.getClasLoader() is a custom method of the ClassLoaderObjectInputStream that is changed in the proposed fix and returns the ClassLoader from the classLoader field. this.getClass().getClassLoader() returns the ClassLoader that loaded the ClassLoaderObjectInputStream. On Tue, Feb 21, 2017 at

[osgi-dev] Question about class loaders

I wonder what the difference is between this.getClassLoader() and this.getClass().getClassLoader() This came up in a proposed fix for the fastbin transport in Aries RSA and I wonder if it should really make a difference:

Re: [osgi-dev] OSGifying an existing application

Christian, I will investigate it, if I can navigate a path through the serialization issues. It is actually looking quite positive. Peter, Well, I wouldn't jump to conclusions too soon, it's still worth a look, a lot of the features will look familiar to OSGi devs. The discovery

Re: [osgi-dev] OSGifying an existing application

My personal expectation is that Jini is entrenched on the Java serialization quagmire that you probably have to work around a lot more problems than the myriad of discovery and transport protocols that are currently available in Java? It is a pity because Jini and OSGi started in the same time