Hey what API holds the statementFinalizer? On Fri, Oct 30, 2009 at 9:57 AM, Josh Gooding <josh.good...@gmail.com>wrote:
> AHHHHHH, I will read the API for the StatementFinalizer. I was looking at > something to do that. Thank you Filip! > > > On Fri, Oct 30, 2009 at 9:53 AM, Filip Hanik - Dev Lists < > devli...@hanik.com> wrote: > >> hi Josh, calling Connection.close() does not close statements and >> resultsets. >> There is an interceptor you can configure called StatementFinalizer that >> does exactly that during the close call. >> >> Filip >> >> >> >> On 10/29/2009 07:17 PM, Josh Gooding wrote: >> >>> I wrote some code on top of the Tomcat's ConnectionPool class. In >>> regular >>> Java based programming if I close a ResultSet with connection.close(), >>> this >>> frees up both the statement and resultset's memory associated with the >>> connection if it was still open. If I close a connection with Tomcat's >>> ConnectionPool, does it also close the statement and resultset's >>> associated >>> with that particular connection or do I need to manually close them? >>> >>> I know best practice is to not rely on anything to be closed >>> automatically, >>> but I inherited a code base and I am looking at making some pretty >>> significant changes to fix some problems, and this is one of them. >>> >>> Thanks in advance, >>> >>> - Josh >>> >>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> >
