Three months ago, we shelved this topic, promising to return to it
later. I would like to reach consensus on this problem now. In a
nutshell: JDBC4 introduces new methods whose signatures contain
generics. Because of this, DataSource implementations can't satisfy both
the JDBC3 and JDBC4 contracts.
So that's not quite true, a JDBC 4.0 DataSource implementation does
satisfy both JDBC 4.0 and JDBC 3.0. I've been looking at if it would be
possible to have a single implementation that worked in both. Ie. would
the reference to new classes and the generics absolutely make the class
not work in JDBC 3.0. Most likely yes, but it's worth throwing out there.
Generics can be compiled jdk 1.5 or higher. And class generated with
jdk1.5 or higher are not
compatible with the older vm s.
anurag
