The ESQL logicsheet could easily be altered (invisibly to the user)
so that calls to Connection are using the Connection object and calls
to the new methods are using the holder class.
True.
I'll have a look..
Will do this ASAP
--
Torsten
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 Excalibu
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 exten
...you mean the EsqlConnection should not implement Connection?
Shocking isn't it?
=8-O yes! :)
And what new methods should it use?
I don't have the slightest idea :)
The ESQL logicsheet could easily be altered (invisibly to the user)
so that calls to Connection are using the Connection object a
Torsten Curdt 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.
...you mean the EsqlConnection should not impl
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.
...you mean the EsqlConnection should not implement Connection?
For E
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 isClose
Berin Loritsch wrote:
Sylvain Wallez wrote:
Berin Loritsch wrote:
Please cross check this version of the Excalibur DataSource, and see
if it works just as well as the old version. If so, I will commit
my changes and we will all be happier.
Of particular interest:
This was compiled on JDK 1.4,
Sylvain Wallez wrote:
Berin Loritsch wrote:
Please cross check this version of the Excalibur DataSource, and see
if it works just as well as the old version. If so, I will commit
my changes and we will all be happier.
Of particular interest:
This was compiled on JDK 1.4, please make sure it work
Ulrich Mayring wrote:
Berin Loritsch wrote:
Please cross check this version of the Excalibur DataSource, and see
if it works just as well as the old version. If so, I will commit
my changes and we will all be happier.
Of particular interest:
This was compiled on JDK 1.4, please make sure it work
Berin Loritsch wrote:
Please cross check this version of the Excalibur DataSource, and see
if it works just as well as the old version. If so, I will commit
my changes and we will all be happier.
Of particular interest:
This was compiled on JDK 1.4, please make sure it works with JDK 1.3.
I wan
11 matches
Mail list logo
