In CodebaseAccessClassLoader, I have been thinking that we might need the
following kind of check to manage exploits that
would know what CodebaseClassAccess instance was being used, and replace it with
one from another class loader.
public static void setCodebaseAccessClassLoader( Codebase
My initial focus, was on just striping away the dependency on RMIClassLoaderSPI
as the "only" way to change class loading behavior. The impetus, of course, was
that Netbeans does not have a trivial way (let alone functional) way to specify
a classpath change (required for the static initializat
Peter Firmstone wrote:
Just thought I'd get a little clarification on how
CodebaseAccessClassLoader should work and whether it needs any further
refinements or tweaks. I'm currently patching
CodebaseAccessClassLoader back into the main trunk, so it can make the
next release.
All references
