Actual mutation of the system classloader can be handled with relative safety in JRE 1.4 and later via a system property 'java.system.class.loader'
This is news to me Steven. This implies that the system classloader would need to query this property to see if it changed any time it attempts to locate a new Class, no? This surprises me. You're positive you can change the system's classloader classpath dynamically just by assigning to this property? You're description of URL custom handlers is pretty good, but you gloss over the registration of the custom handlers. Don't you still need to install your own handler factory? Doesn't that require a JVM arg at startup, i.e. you cannot install it once the JVM is up? I'm still concerned about the use of an embedded Ant regarding the custom handler factory. Maybe things have changed since I looked at them, but I felt that custom URL handlers' registration or discovery was not convenient or flexible enough the way the JDK implemented it. --DD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
