On 02/01/2015 10:56 AM, Alan Bateman wrote:
I see. But isn't URL.setURLStreamHandlerFactory() enough for that
purpose? It can only be set once, but there can only be *one*
container that wants it's jar protocol handler configured system-wide.
This a good question as it brings up the scenari
On 02/01/2015 10:56 AM, Alan Bateman wrote:
On 31/01/2015 23:47, Peter Levart wrote:
I agree. Putting the order on the SPI API is not the right solution.
The order should be configured in one place. But there needs to be
some kind of handle each service exposes for order configuration to
re
On 31/01/2015 23:47, Peter Levart wrote:
I agree. Putting the order on the SPI API is not the right solution.
The order should be configured in one place. But there needs to be
some kind of handle each service exposes for order configuration to
reference. So one idea how to extend the Service
Hi Bernd,
On 02/01/2015 01:14 AM, Bernd wrote:
Hello,
What about simply rejecting overlapping programmatic registrations,
This can't work by registering URLStreamHandlerFactory objects as they
don't announce their supported protocols. Perhaps registering
URLStreamHandler objects directly
