Thanks, I don't know much about JNDI (apart from in general terms what it is); why would doing it this way be a good thing?
Howard > -----Original Message----- > From: Robert Taylor [mailto:[EMAIL PROTECTED]] > Sent: 15 August 2002 12:10 > To: Struts Users Mailing List > Subject: RE: Connection pool question > > One solution might be to define several datasources in your > application/servlet container where each datasource corresponds to its > respective database. > Then use JNDI to access the datasources from your application. > > robert > > -----Original Message----- > From: Howard Miller [mailto:[EMAIL PROTECTED]] > Sent: Thursday, August 15, 2002 6:47 AM > To: '[EMAIL PROTECTED]' > Subject: Connection pool question > > Hi, > > Newbie, JDBC connection pool question: > > My application uses a central control database. This is ok, and I > can see how to use a connection pool for my application to access this. > > BUT... The application allows a user to recover data from a range of > additional databases. That is the central database verified logins etc and > then lists a number of databases for the user to connect to. > > I am very unsure how to handle this "sub -connection". I have a > number of thoughts... all bad: > 1. Set up connection pools to ALL possible databases (there are less > than 10), at the start in the application scope. > 2. Set up a dedicated connection in the session scope. > 3. Set up a dedicated connection in the request scope (cgi style). > > I don't like any of these answers. Anybody have experience of this > sort of "dynamic database connection" or have any thoughts. > > Regards, << File: ATT00047.txt >> << File: ATT203342.txt >> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
