I'm reposting due to a lack of response. I've searched the archives,
and I'm doing everything mentioned there, yet I still can't seem to
get the default InitialContext to load the jndi.properties from the
application's classpath.
PREVIOUS POST:
How do I make the default InitialContext use the
McDowell, Mark [EMAIL PROTECTED] writes:
I'll preface this with *I am NOT an expert* :)
Me neither.
The only information I'm aware of is that if the jndi.properties
file is in the CLASSPATH, it should be found Try adding
WEB-INF/classes to the CLASSPATH prior to starting Tomcat...
How do I make the default InitialContext use the jndi.properties in
my application's WEB-INF/classes directory?
I'm using 3.2.2 with the correct Interceptor:
RequestInterceptor className=org.apache.tomcat.request.Jdk12Interceptor /
I'm open to upgrading my Tomcat if that's the only way.
Along those same lines, what's the recommended approach for sharing one
installation of tomcat with multiple users?
Should they each create their own server.xml and set the "home"
attribute of the ContextManager to a location beneath their home
directory, specifying the -f option to
paths relative to its "home" attribute. I suppose I can live with
absolute paths for now, though.
Kief Morris wrote:
Jim Crossley typed the following on 09:23 AM 2/6/2001 -0500
Along those same lines, what's the recommended approach for sharing one
installation of tomcat with mult
Hi Peter,
Unfortunately, there's no foolproof way to do what you're trying to do.
The limitation is imposed on the client-side. Your success depends on
how much control you have over your users, i.e. it becomes a training
issue.
A good description of the issues involved is on page 134 of Hans
