I found the problem. Apparently I was picking up a rogue commons-pool
jar from somewhere, likely Tomcat. It seems happier now.
Brad
-Original Message-
From: Cloves Carneiro Jr. [mailto:[EMAIL PROTECTED]
Sent: Friday, November 21, 2003 3:43 PM
To: Apache Torque Users List
Subject: RE:
That, too, is what I am using, or at least attempting to use.
Brad
-Original Message-
From: Cloves Carneiro Jr. [mailto:[EMAIL PROTECTED]
Sent: Friday, November 21, 2003 3:43 PM
To: Apache Torque Users List
Subject: RE: MySQL driver
I am using org.apache.torque.dsfactory.SharedPoolData
When I run it I am told that com.mysql.jdbc.Driver is not supported by
the org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS datasource.
What pooling are you using, if any?
Brad
-Original Message-
From: Cloves Carneiro Jr. [mailto:[EMAIL PROTECTED]
Sent: Friday, November 21, 2003 3:
Have any of you successfully used MySQL with Torque using the current
driver (com.mysql.jdbc.Driver)? It seems that support is fine for the
org.gjt.mm.mysql.Driver, but that is now extinct.
Brad Peterson
Architect
SunGard Online
Hey all,
It seems that logging is lacking documentation (not a surprise) for
the 3.1 release. Torque is using the commons logging, which in the
tarballs is specified to use the simple logger, yet Torque.properties is
set to use log4j. I am trying to turn on logging (log4j) and have had
to wa
