You can, however, use JarFile and JarInputStream objects as long
as you're careful to close everything properly - I got it to work on
Windows too (where there were problems with the JAR file being locked).
We may want to make "file:" URLs a special case and handle them ourselves
to avoid the bugs you refer to. This would also obviate the need for the
/tmp directory since nothing would be locked.
Aaron
On Fri, 24 Nov 2000, Rickard �berg wrote:
> !"#%!"#&%
>
> <freaking mad/>
> JarURLConnections are so f#!"&g buggy!! it's a god damn MESS! And they
> KNOW about it!! Source comment: "this is a mess and a hack for beta 3.
> Clean up soon".. DUH! SOON!?!?!? How about getting it right AT ALL!??
> GEEEZUZ.. no wonder we have problems with hot deployment.. they CACHE
> all connections to Jar files. And do you think it would help to provide
> our own implementation through the standard URLStreamHandler
> interface??! Noooo, they simply create a new URL object *disregarding*
> any custom handlers... *sigh*... damn newbies...
>
> Feel much better now.
>
> /R
>
>
