In Avalon Excalibur, we want to make our Connection Pooling code
future compatible with JDK 1.4. We currently do it with conditional
compiling, and renaming some classes. I find this to be a clumsy
solution, and leads to questions from people not familiar with the
build process. Almost all the new methods except the new transaction
handling methods can be included in the JdbcConnection class.
The issue is the SavePoint class. SavePoint is new to the JDBC 3.0
collection, and is accessed from the Connection object. It is used
to allow you to make Save Points in a transaction--so you can restore
to a SavePoint and try an alternate solution. The problem is, in order
to remain compatible in JDBC 2.0 environments, we need to have a
SavePoint class that can do absolutely nothing.
We would have to have a class in the jar like this:
public class java.sql.SavePoint {}
During the compile, if a Jdbc3.0 environment was detected, the class
would be excluded from the build and the Jdbc3Connection class would
be included. The opposite would happen when we don't have Jdbc3.0
available.
Sun guards the java.* classes jealously, and I need to know if this
is really a solution.
--
"Those who would trade liberty for
temporary security deserve neither"
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
