?
Ian.
-Original Message-
From: ps [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 04, 2003 4:35 PM
To: Tomcat Users List
Subject: DBCP+TOMCAT 3.2.4 (-4.1.x WORKED OK)
Greetings,
I'm downgrading my web application to work on tomcat 3.2.4 (initially
was developed and tested OK
?
-Original Message-
From: ps [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 04, 2003 4:35 PM
To: Tomcat Users List
Subject: DBCP+TOMCAT 3.2.4 (-4.1.x WORKED OK)
Greetings,
I'm downgrading my web application to work on tomcat 3.2.4 (initially
was developed and tested OK on tomcat
On Tue, 2003-02-04 at 22:38, Sean Dockery wrote:
Weird that your envCtx.lookup is done on /jdbc/ngincaredb. I've never seen
it done on an absolute path before. :-)
Yes, I don't know why I put it like that, maybe I was guided by an
example, maybe it was a writing mistake that worked fine in
Please, how should I interpret the exception message header below:
javax.naming.NoInitialContextException: Need to specify class name in
environment or system property, or as an applet parameter, or in an
application resource file: java.naming.factory.initial
I'm using jdk1.4.1 (SUN) and tomcat
On Wed, 5 Feb 2003, ps wrote:
Date: 05 Feb 2003 11:48:15 +
From: ps [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: Re: DBCP+TOMCAT 3.2.4 (-4.1.x WORKED OK)
Please, how should I interpret the exception message header
On Wed, 2003-02-05 at 17:07, Craig R. McClanahan wrote:
On Wed, 5 Feb 2003, ps wrote:
Date: 05 Feb 2003 11:48:15 +
From: ps [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: Re: DBCP+TOMCAT 3.2.4 (-4.1.x WORKED OK
You can still use DBCP in Tomcat 3.x, right? You just can't deploy the
data source through JNDI automatically...
Could this be done manually? That is, could I not write a context listener
that deployed the DBCP factory through JNDI when the application was
started? I know that it would
On Wed, 5 Feb 2003, Sean Dockery wrote:
Date: Wed, 05 Feb 2003 11:03:00 -0700
From: Sean Dockery [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: Re: DBCP+TOMCAT 3.2.4 (-4.1.x WORKED OK)
You can still use DBCP in Tomcat 3.x
Greetings,
I'm downgrading my web application to work on tomcat 3.2.4 (initially
was developed and tested OK on tomcat 4.1.18). I'm using DBCP1.0.
problem:
I can't get a datasource through JNDI that usually worked fine in tomcat
4.1.x, instead I'm getting an exception! Since I'm not
: DBCP+TOMCAT 3.2.4 (-4.1.x WORKED OK)
Greetings,
I'm downgrading my web application to work on tomcat 3.2.4 (initially
was developed and tested OK on tomcat 4.1.18). I'm using DBCP1.0.
problem:
I can't get a datasource through JNDI that usually worked fine in tomcat
4.1.x, instead I'm
Whoops, and commons-pool.jar?
-Original Message-
From: ps [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 04, 2003 4:35 PM
To: Tomcat Users List
Subject: DBCP+TOMCAT 3.2.4 (-4.1.x WORKED OK)
Greetings,
I'm downgrading my web application to work on tomcat 3.2.4 (initially
Weird that your envCtx.lookup is done on /jdbc/ngincaredb. I've never seen
it done on an absolute path before. :-)
Please provide all of the parameters that you are declaring under the
ResourceParams section. (I don't want to know your username and
password--I just want to know the entire
12 matches
Mail list logo
