On 11/21/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
> Especially as JDBC says:
>
> "Calling the method close on a Connection object that is already
> closed is a no-op."
>
> I think this came up before though, so I suspect there's a good reason.
>
> Hen
>
There is a long history on this. While
Especially as JDBC says:
"Calling the method close on a Connection object that is already
closed is a no-op."
I think this came up before though, so I suspect there's a good reason.
Hen
On Nov 19, 2007 4:28 PM, <[EMAIL PROTECTED]> wrote:
> To Whom It May Concern:
>
> Why is it necessary to th
To Whom It May Concern:
Why is it necessary to throw a new SQLException("Already closed") when
the purpose of the close() method is to close the connection. Seems to
me this Exception is not necessary.
In my code (Tomcat/DBCP/iBATIS) apparently iBATIS is trying to close an
already closed connec
