Apparently the problem is quiet old:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg01282.html
It was recently discussed on commons-dev
http://marc.theaimsgroup.com/?l=jakarta-commons-devm=101538994027435w=2
My suggestion would be to ask on [EMAIL PROTECTED] to see whether the problem
was
:Re: JDBC version problems
But the problem isn't the methods, but the new classes. For example,
one of the new methods on Connection is:
Savepoint setSavepoint();
No matter what the implementation of this method is, the 1.2 JRE will
not supply a Savepoint class. That will prevent
Ray,
Have you considered using jdbc-2.0jar as commons-dbcp has done?
At 12:52 PM 8/9/2003 -0400, you wrote:
But the problem isn't the methods, but the new classes. For example,
one of the new methods on Connection is:
Savepoint setSavepoint();
No matter what the implementation of this method
I think that I will abandon writing a log4j connection pooling class and
instead suggest that users use the commons-dbcp package. I looked it
over and it does not require anything special from the client code;
everything is configured at run-time. Therefore there should be no
issue with
Hello all,
As some of you know, I've been working on JDBC-based appenders in the
sandbox. I wanted to create a connection pool for environments where no
such pool existed so that the JDBC appender would not have to create a
new connection for every log message.
If you've never thought about
But the problem isn't the methods, but the new classes. For example,
one of the new methods on Connection is:
Savepoint setSavepoint();
No matter what the implementation of this method is, the 1.2 JRE will
not supply a Savepoint class. That will prevent the the Connection
implementation from
