I resolved my own problem, and should have caught it along time ago. I
needed to install the standard 4.1.18 to access JNDI resources. Hope that
this might help someone else in the future.
-Original Message-
From: Nicole Hibbard [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 13, 2003
Nicole Hibbard wrote:
I resolved my own problem, and should have caught it along time ago. I
needed to install the standard 4.1.18 to access JNDI resources. Hope that
this might help someone else in the future.
I'm using 4.1.12 and jndi resources work fine :) .
-Original Message-
I was using the LE version and needed to use the standard which supports
JNDI resources.:)
-Original Message-
From: Peng Tuck Kwok [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 14, 2003 4:18 PM
To: Tomcat Users List
Subject: Re: Name jdbc:comp is not bound in this context
Nicole
I think the LE version just omits the xml parsers and just uses the one
that the jdk 1.4 has. There is no mention of omitting key features like
that in the LE versions. Can someone else comment?
Nicole Hibbard wrote:
I was using the LE version and needed to use the standard which supports
JNDI
I've gone through every resource I have in trying to test a connection to
MySql database.
I am using Tomcat 4.1.18-LE and MySql 3.23.53 and java 1.4.1_01.
I set priveleges on MySql, put the mm.sql driver's jar in common/lib.
I set my Classpath Variable
If someone doesn't have time to help me, but knows somewhere else I might be
able to get help, please let me know. If I don't get this working by
tonight then I'll probably have to nix using Tomcat alltogether and try
something different and I don't want that to happen. I appreciate any help
I
Nicole,
Not sure if this was answered, but I'll give it a try. When I had this
problem, I found that I needed to add useNaming=true to both the Host
... entry and to the Context ... entry.
Sincerely,
Pantek Incorporated
Justin L. Spies
URL: http://www.pantek.com
Ph 440.519.1802
Fax
Thanks for the reply :). Unfoutunately I added the useNaming=true and I
still have the same results. I'm really stuck here... do you have any other
suggestions.
-Original Message-
From: Justin L. Spies [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 13, 2003 3:31 PM
To: 'Tomcat Users
Is this an issue encountered by users of tomcat 4.1.18.Le? Should i try
reinstalling and configuring an earlier version? I've see serveral
discussion regarding this topic and I've tried everything suggested... what
should I do now?
-Original Message-
From: Nicole Hibbard [mailto:[EMAIL
