Re: Question about Tomcat Documentation

2003-08-23 Thread Peter Harrison
From previous message:

 I was thinking that maybe now there's a default factory that can handle 
 things, but now when I run the App I get an exception:

 Cannot load JDBC driver class 'null'

 Which makes me think the default factory is not correct. So is the 
 documentation wrong, or are there cases where it can work with the 
 default factory?

On Sat, 23 Aug 2003 09:16, Madere, Colin wrote:
 Possibly the same as the issue in this recent thread:

 Tomcat 4.1 DefaultContext Bug?, regarding DefaultContext resources not
 being available to implicit contexts, check archives.

Yes, this sounds like exactly the problem I am having. It is working when the 
resource is put into the standard Context, but not when its put into the 
Global Resources or Default Context.

Is there a solution anyone knows of?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Question about Tomcat Documentation

2003-08-22 Thread Derek Chen-Becker
Hi,
I'm moving a server from 4.0.6 to 4.1.27 and I noticed something 
strange about the included 4.1.27 documentation. In the JNDI Resource 
HOWTO, the section on JDBC resources doesn't explicitly add a factory 
parameter, and it also says this about DBCP support:

NOTE - The default data source support in Tomcat is based on the DBCP 
connection pool from the Jakarta Commons  subproject. However, it is 
possible to use any other connection pool that implements 
javax.sql.DataSource, by writing your own custom resource factory, as 
described below.

I was thinking that maybe now there's a default factory that can handle 
things, but now when I run the App I get an exception:

Cannot load JDBC driver class 'null'

Which makes me think the default factory is not correct. So is the 
documentation wrong, or are there cases where it can work with the 
default factory?

Thanks,

Derek

--
--
Derek Chen-Becker
Senior Network Engineer
CPI Corp, Inc.
1706 Washington Ave
St. Louis, MO 63103
Phone: 314-231-1575 x6014
Fax:   314-613-6724
[EMAIL PROTECTED]
PGP Key available from public key servers
Fingerprint: 1C34 D81E D8A0 641D 6C8C  E952 3B15 693F 9184 BC58
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: Question about Tomcat Documentation

2003-08-22 Thread Madere, Colin
Possibly the same as the issue in this recent thread:

Tomcat 4.1 DefaultContext Bug?, regarding DefaultContext resources not
being available to implicit contexts, check archives.

Also, check to make sure you have the url parameter rather than the
driverName I think it was called under 4.0.

-Original Message-
From: Derek Chen-Becker [mailto:[EMAIL PROTECTED] 
Sent: Friday, August 22, 2003 2:15 PM
To: Tomcat Users List
Subject: Question about Tomcat Documentation


Hi,
 I'm moving a server from 4.0.6 to 4.1.27 and I noticed something 
strange about the included 4.1.27 documentation. In the JNDI Resource 
HOWTO, the section on JDBC resources doesn't explicitly add a factory 
parameter, and it also says this about DBCP support:

NOTE - The default data source support in Tomcat is based on the DBCP 
connection pool from the Jakarta Commons  subproject. However, it is 
possible to use any other connection pool that implements 
javax.sql.DataSource, by writing your own custom resource factory, as 
described below.

I was thinking that maybe now there's a default factory that can handle 
things, but now when I run the App I get an exception:

Cannot load JDBC driver class 'null'

Which makes me think the default factory is not correct. So is the 
documentation wrong, or are there cases where it can work with the 
default factory?

Thanks,

Derek

-- 
--
Derek Chen-Becker
Senior Network Engineer
CPI Corp, Inc.
1706 Washington Ave
St. Louis, MO 63103
Phone: 314-231-1575 x6014
Fax:   314-613-6724
[EMAIL PROTECTED]
PGP Key available from public key servers
Fingerprint: 1C34 D81E D8A0 641D 6C8C  E952 3B15 693F 9184 BC58
--


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]