On 8/27/18 10:47 AM, Alan Bateman wrote:
On 27/08/2018 15:47, David Lloyd wrote:
:
AFAIK any code would expect that resources available as streams would
generally also be available as URLs. I'm not sure that distinguishing
between basic and advanced code really clarifies anything in terms of
the question.
I think you've mis-read my mail. I was just observing that
newbie/simple programs executed by the source file launcher are
unlikely to need to locate the class bytes via the getResourceXXX
APIs. That doesn't mean the issue should be ignored, it just means it
may not be high priority. In any case, I see Jon has created an issue
to track this. Also the URL protocol handler pluggability that was
added in Java SE 9 will help as it makes me it easy for the
jdk.compiler module to include a URLStreamHandlerProvider.
-Alan
Alan,
It looks like we don't even need to register a URLStreamHandlerProvider,
we can provide the URLStreamHandler when we create the URL. :-)
-- Jon
