> On 14 Feb 2017, at 18:37, Paul Sandoz <[email protected]> wrote: > >> >> On 14 Feb 2017, at 05:58, Chris Hegarty <[email protected]> wrote: >> >> >>> On 13 Feb 2017, at 22:52, Paul Sandoz <[email protected]> wrote: >>> >>> Hi, >>> >>> Please review. >>> >>> http://cr.openjdk.java.net/~psandoz/jdk9/JDK-8174151-url-class-path-loader/webrev/index.html >> >> If I understand this correctly then the only optimisation ( by-pass of >> openConnection ), which is causing the problem, is when the URL >> is of the form “jar:file:xxxxx!/“, right? If so, you could limit the scope >> of your changes to only fall back to Loader when the nested URL >> has a “file” protocol. This would give you MR JAR functionality for >> "jar:http://xxx”, which is fairly common. >> > > We need to tunnel, by default, all jar: URL resources through the JarLoader > which creates and caches the runtime versioned JarFile and returns an > appropriately URL (to a versioned resource if necessary).
Ok, thanks Paul. -Chris.
