On Thu, 30 Jan 2003 04:40, Sylvain Wallez wrote: > Wow, never noticed such a beast existed. This means that under the > hoods, JDK URL handling depends on the calling class. > > This may be a _very cool_ solution to make the source resolving > machinery available to classes that aren't aware of it.
Not that kool. Actually in many ways it sucks. Several protocols have the concept of nested protocols (such as jar: protocol) and the nested protocol will actually delegate to system URL handlers and ignore yours. So lets pretend you have the protocol "baz". You could not use it like the following without setting it as a system handler. jar:baz://someBazURL/myArchive.jar!/META-INF/avalon.xml -- Cheers, Peter Donald *-------------------------------------------------* | An eye for eye only ends up making the whole | | world blind. - Gandhi | *-------------------------------------------------* --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
