Sylvain Wallez wrote:
Berin Loritsch wrote:
So it seems to me that a simple way to avoid this JDBC mess (at least in Cocoon) would be for ESQLConnection to _hold_ a Connection instead of _extending_ it.
For ESQLConnection, definitely. For Excalibur DataSource, it extends
the close() and isClosed() methods to provide pooling. Any other
methods that we extend are taken care of in the proxy object so we can
still work with JDK 1.3 and JDK 1.4. At least that is the theory.
Since close() and isClosed() are JDBC2, maybe compiling the full JDBC3 version with JDK 1.4 and use it with JDK 1.3 may work ?
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
