Re: URLStreamHandlerFactory

2013-01-17 Thread Mark Thomas
On 17/01/2013 14:02, e e wrote: > Can anyone please provide me this information please. Sorry for being > persistent!! > > I am still not clear why a URLStreamHandlerFactory is required for JNDI!!! It isn't. > I thought Context.lookup() is what the web-apps will do! They do. > Why would th

Re: URLStreamHandlerFactory

2013-01-17 Thread e e
Can anyone please provide me this information please. Sorry for being persistent!! I am still not clear why a URLStreamHandlerFactory is required for JNDI!!! I thought Context.lookup() is what the web-apps will do! Why would the web-apps want to use a new URL("jndi://"); Where/why does tom

Re: URLStreamHandlerFactory

2013-01-16 Thread e e
Thanks for the response. I will move to Tomcat-7. But, I am still not clear why a URLStreamHandlerFactory is required for JNDI!!! I thought Context.lookup() is what the web-apps will do! Why would the web-apps want to use a new URL("jndi://"); Where/why does tomcat have to use jndi URLs to fetc

Re: URLStreamHandlerFactory

2013-01-15 Thread Mark Thomas
On 15/01/2013 19:09, Christopher Schultz wrote: > Sriram, > > On 1/15/13 12:50 PM, e e wrote: >> [I a]m trying to understand why WebAppLoader does a >> URL.setURLStreamHandlerFactory(). > > Presumably, it's important to handle URLs in a custom way for web > applications. No. It is because Tomc

Re: URLStreamHandlerFactory

2013-01-15 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Sriram, On 1/15/13 12:50 PM, e e wrote: > [I a]m trying to understand why WebAppLoader does a > URL.setURLStreamHandlerFactory(). Presumably, it's important to handle URLs in a custom way for web applications. > I see that a protocol handler is b