Sylvain Wallez wrote:
Berin Loritsch wrote:
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 ?
As I mentioned before, we have already done that. For some reason,
Cocoon complained about invalid clss files and such.
Can you confirm if my changes work on JDK 1.3? I think it is the
cleanest solution and allows people with JDK 1.3 to build the library
and it will still work with JDK 1.4.
Cocoon is the problem application for this package, which is why I
wanted you guys to verify it.
