RE: [Proxool-developer] Connections closed and open

[Bill H. <bi...@lo...>]

Hi John,

On Thu, 2004-02-05 at 17:20, Hume, John - NA US HQ Delray wrote:

> If the instance of the Connection-proxy is NOT the same one, then this
> problem goes away: calling close() returns the underlying Connection to the
> pool and can set the state of the Connection proxy so that any subsequent
> attempt to use it can throw "SQLException: connection already closed" or
> something like that.

It *is* the same instance of the proxy connection. So this is a problem
I believe. I quite like the idea of wrapping up the connection inside a
disposable wrapper. That would certainly solve this issue.

It's not a quick fix however. There isn't a clean separation from the
wrapper and the internal component that knows about the state of the
connection. It would be good to clean it up though. At the same time, we
could get rid of the redundant abstraction we needed when dealing with
multiple JDKs (back before we used Cglib).

We certainly wouldn't do this before 0.10 (0.9 is due soon to add
DataSource implementation). But maybe it should be done before 1.0.

- Bill