On 10/27/2012 3:31 AM, Simon IJskes - QCG wrote:
On 26-10-12 23:49, Gregg Wonderly wrote:
I wonder if Peter pulled it out when some of the other stuff he was
pushing into the build created some problems late last year? Humm,
it should be in there.

I will take a look at it.

I've taken a shortcut, and reduced the impact a little bit. Is a Spi enough for you? You can always plugin a dynamic variant.

Here's some more of what was covered by my purposed patches.

The primary issue for netbeans, was that the "SystemClassLoader" was not the appropriate parent class loader for downloaded code. The proper parent, is the ClassLoader of the module which is performing the task of resolving the classes. So, that was the primary thing I needed to take care of. I decided to just cover every method which RMIClassLoaderSPI provided interactions for, so that there was an actual SPI replacement opportunity. But, I wanted to remove the use of the term RMI, because that's one "old bone" that makes people believe that Jini is not really anything different.

Gregg

Reply via email to