db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johnny Kewl" <j...@kewlstuff.co.za>
Subject Re: embedded db and connection pooling
Date Wed, 04 Jun 2008 16:50:23 GMT

----- Original Message ----- 
From: "Alan Burlison" <Alan.Burlison@sun.com>
To: "Derby Discussion" <derby-user@db.apache.org>
Sent: Wednesday, June 04, 2008 4:23 PM
Subject: Re: embedded db and connection pooling

> 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.

Ah, yes true, can make the webapp pools redeployable, but what do you do for 
the first webapp, and the server setup.
You right, JNDI and embedded database are actually contradictory idea's, as 
far as plug and play goes.

View raw message