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!
T
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://"); Wher
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 jn
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
our app-server
> makes it difficult) (We run tomcat as one of the components in our
> server) (Similar to any j2ee server)
I believe the WebappLoader only runs the
URL.setURLStreamHandlerFactory call a single time when it starts up.
At that point, your webapp's code will not be available t
- Am trying to understand why WebAppLoader does a
URL.setURLStreamHandlerFactory().
- I see that a protocol handler is being set for "jndi://" protocol. Our
apps' do NOT use JNDI urls. I believe tomcat 6 has NOT used the jndi url
anywhere in its codebase.
- What feature in tomcat
