It would seem a lot less work to fill up a hashtable with parameters and
get a vanilla JNDI context for your external nameserver independent of
the internal context used for web-app resources. What's the point of
looking up web-app resources in an external directory when they can't be
shared anyhow
/apache/naming/java/javaURLContextFactory.java).
Yoav Shapira
Millennium Research Informatics
>-Original Message-
>From: Dave Bender [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, June 16, 2004 12:34 PM
>To: Tomcat Users List
>Subject: RE: Configuring JNDI for tomcat
>
-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 8:37 AM
To: Tomcat Users List
Subject: RE: Configuring JNDI for tomcat
Hi,
You're right, and this is in the FAQ:
http://jakarta.apache.org/tomcat/faq/misc.html#externalJndi.
Yoav Shapira
Millennium Res
Users List; Russ Leong
>Subject: RE: Configuring JNDI for tomcat
>
>Tomcat does not expose a naming service on any port at all, so far as I
>know. It just offers an internal API to JNDI in which it populates a
>namespace.
>
>
>---
Tomcat does not expose a naming service on any port at all, so far as I
know. It just offers an internal API to JNDI in which it populates a
namespace.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
Sounds like nothing's running on localhost port 1099. I'm not a Tomcat expert so I
don't know if Tomcat is supposed to be exposing its Naming Service on that port. If
it is, it isn't there.
Dave
-Original Message-
From: Russ Leong [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 15, 200
