Sylvain Wallez wrote:
Berin Loritsch wrote:
What about the
URLClassLoader( ClassLoader parent, URL[] paths, URLConnectionHandler
handler );
constructor?
Wow, never noticed such a beast existed. This means that under the
hoods, JDK URL handling depends on the calling class.
:)
I believe it was introduced in JDK 1.3 along with dynamic proxies.
This may be a _very cool_ solution to make the source resolving
machinery available to classes that aren't aware of it.
In fact I think it would be better than what we have now--we just
need to figure out how to handle certain things like the "cocoon:"
protocol that don't necessarily follow normal URL semantics.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
