Kyle F. Downey wrote:
> Remy,
>
> Do you happen to know if the patch I submitted for the context
> ClassLoader was ever inspected or merged in? I never saw a reply.
>
Sorry, this was a personal reply not meant for the list.
--kd
Remy,
Do you happen to know if the patch I submitted for the context
ClassLoader was ever inspected or merged in? I never saw a reply.
--kd
If you are concerned about security, allowing a web app to set the
default URLStreamHandler is not a very secure thing to do because
it gives the webapp the ability to see all URL streams globally in the JVM.
When using Tomcat with the Java SecurityManager, web apps are not normally
granted per
- Original Message -
From: "Kyle F. Downey" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 18, 2001 6:25 PM
Subject: setURLStreamHandlerFactory--why?
> I'm working with the latest b4-dev from CVS.
>
> Is there a rea
I'm working with the latest b4-dev from CVS.
Is there a reason the StandardLoader establishes a URLStreamHandlerFactory
(a precious resource, since you can set it only once) just for the "jndi:"
protocol? If all it's used for is to find the protocol handler, that could
be done less intrusively b
