> You're implementation looks OK. I assume you are calling the .close() > method (to put the conneciton back in the pool) when you are done with the > connection in each request. The destructor on the connection wrapper will > call .close() if you forget to, but it is good form to call it > explicitely. Yes I am. Since all other calls besides the initial getConnection() are the same as the original non-pooled db module, I left the rest of my code out of the example I posted.
> I noticed that you have commented out the call to .stopExpiration() in the > destructor for the base servlet. I would remove it entirely, since I > can't think of a good reason to ever call it, except maybe within a test > suite. I've got a question about this. To be honest, it's been a while since I've looked at that code, and I don't remember exactly why I commented it out. But, just looking at the code now, it seems like a good idea to have it in there. The destructor is called when the app server shuts down, right? So shouldn't I make a call to the pooling module to allow itself to terminate properly? Why would you take it out completely? --John ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
