Re: DBCP+TOMCAT 3.2.4 (->4.1.x WORKED OK)

2003-02-05 Thread Craig R. McClanahan
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 W

Re: DBCP+TOMCAT 3.2.4 (->4.1.x WORKED OK)

2003-02-05 Thread Sean Dockery
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 invol

Re: DBCP+TOMCAT 3.2.4 (->4.1.x WORKED OK)

2003-02-05 Thread ps
<[EMAIL PROTECTED]> > > Subject: Re: DBCP+TOMCAT 3.2.4 (->4.1.x WORKED OK) > > > > Please, how should I interpret the exception message header below: > > > > javax.naming.NoInitialContextException: Need to specify class name in > > envi

Re: DBCP+TOMCAT 3.2.4 (->4.1.x WORKED OK)

2003-02-05 Thread Craig R. McClanahan
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) > > Pl

Re: DBCP+TOMCAT 3.2.4 (->4.1.x WORKED OK)

2003-02-05 Thread ps
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

Re: DBCP+TOMCAT 3.2.4 (->4.1.x WORKED OK)

2003-02-05 Thread ps
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

RE: DBCP+TOMCAT 3.2.4 (->4.1.x WORKED OK)

2003-02-05 Thread ps
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.

RE: DBCP+TOMCAT 3.2.4 (->4.1.x WORKED OK)

2003-02-05 Thread ps
to also copy commons-collections.jar which dbcp needs? > > 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,

Re: DBCP+TOMCAT 3.2.4 (->4.1.x WORKED OK)

2003-02-04 Thread Sean Dockery
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 li

RE: DBCP+TOMCAT 3.2.4 (->4.1.x WORKED OK)

2003-02-04 Thread Zabel, Ian
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 (initi

RE: DBCP+TOMCAT 3.2.4 (->4.1.x WORKED OK)

2003-02-04 Thread Zabel, Ian
st 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 4.1.18). I'm using DBCP1.0. problem: I can't get a datasource through JNDI that usually worked fine

DBCP+TOMCAT 3.2.4 (->4.1.x WORKED OK)

2003-02-04 Thread ps
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 awar