Can't we extend a BaseAbstractEqslConnection and just add the methods that change from one JDK to the other?
hmm.... I doubt the AbstractEsqlConnection will change that often so this should not be too hard to maintain.
If we would go this way I'd propose to name it AbstractJdbcConnection
since then there is no relation to esql anymore. Maybe it should also better live in a different package.
Could also be useful for other components that use JDBC directly...
Hm... I start to like it... -- Torsten
