Johnny Kewl wrote:
I'm not sure if the driver makes any diffs, as long as when you undeploy the web app, TC lets the dB go, and when you redeploy that web app it makes the new connection pool, I'm not sure the driver makes any diffs. I'm guessing... but I think the core issue is to stop TC making those connections "when it starts", ie it must not be global, because then it holds the connections for other webapps. If the driver remains visible... not sure if thats a problem, its just a library in a classpath?
The issue is that you don't have a truly 'stand alone, drop in & deploy' webapp if it requires you to install stuff into the container's lib directory and fiddle with the server.xml file before deploying the app.
-- Alan Burlison --
