> Except that the javax.sql.DataSource API still includes this method signature, so we
>need to do something. I guess
> it would probably be better to return a "not implemented" exception of some sort,
>then just return a "regular"
> connection like it does now.
Yes or just a normal connection that the user auto closes when he calls close,
so won't be pooled or anything.
> > What should be done is testing the isClosed() method before given the Connection
>to the request.
> > If the database closes the connection will the connection.isClosed() return a
>boolean true then?
>
> My experience has been that this is not sufficient. You don't find out that the
>driver connection got closed until
> you try to submit an SQL statement for execution -- what we need to be able to
>configure is a very low-overhead SQL
> call that can be tried before returning the connection to the user.
What about a extra rollback() call right before given it back to the request?
Or is the driver/connection smart enough that the rollback doesn't do anything
(because nothing happend)
and it doesn't send it to the server?
johan
