On Thu, Nov 7, 2019 at 12:38 PM <ma...@apache.org> wrote:

> +         * One option to resolve this issue is to use a custom URL scheme
> for
> +         * resource URLs. This would allow us, via registration of a
> +         * URLStreamHandlerFactory, to control how the resources are
> accessed
> +         * and ensure that all access go via the cache We took this
> approach for
> +         * war: URLs so we can use jar:war:file: URLs to reference
> resources in
> +         * unpacked WAR files. However, because
> URL.setURLStreamHandlerFactory()
> +         * may only be caused once, this can cause problems when using
> other
> +         * libraries that also want to use a custom URL scheme.
>
>
That's how it was done in Tomcat 7, and going down that route would mean
bringing back everything including the classloader bindings. So let's try
to avoid it.

Rémy

Reply via email to