Modularizing URLStreamHandlerFactory

[Alan Bateman]

On 18/06/2012 02:20, David Holmes wrote:
>
> When we added UncaughtExceptionHandler we recognized the desirability 
> to have a "per app" default rather than only having the global 
> default, but there was/is no "application context" to define-in or 
> extract-from the UEH. I don't see how a modular JRE has changed that 
> at all? 
It hasn't, but at some point there will be support added to allow 
containers arrange things so it can load modules that may have a 
different version to that loaded by the container itself. So there may 
be notions "per app" further up the stack but that doesn't make it any 
clearer as to whether UHE is a good candidate on using services.

> Even if you say the UEH is a service, what is the scope/context of 
> that service?
>
> Further, what additional class support do services drag into the 
> runtime? Are these classes that are already in the base module?
The services support is part of the proposal language and module system. 
ServiceLoader is in the base module.

-Alan