application-server-managed database pools are great, they take all the work out of writing your own pooling implementation, and are normally better at it too. furthermore you get to label the pool in a generic way so that your application only needs to acquire the JNDI context and pluck out the datasource (which returns connections). the way in which database pools are setup inside the application server will be app-server specific, but the major players out there (bea, jboss, tomcat) all have the ability to do so. it's a no-brainer for j2ee web applications of yuor mid-sized nature I think.
> -----Original Message----- > From: Scott Purcell [mailto:[EMAIL PROTECTED] > Sent: 16 November 2004 21:35 > To: [EMAIL PROTECTED] > Subject: Database Pooling > > > I am developing a mid-sized application, which will use JSP > Model 2 Architecture. Currently I have a class that does > Database Pooling, but I am curious about some threads I see > time to time. > > I have noticed that some developers on this list refer to > Tomcats Database Pooling. It looks like there are some hooks > into the deployment file. So I guess my question is as > follows. does Tomcat offer this type of pooling? and if so, > is it good, and is it portable? Links, references would be great. > > Thanks, > Scott > > > > > > > <FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLUE> ------------------------------------------------------- QAS Ltd. Developers of QuickAddress Software <a href="http://www.qas.com";>www.qas.com</a> Registered in England: No 2582055 Registered in Australia: No 082 851 474 ------------------------------------------------------- </FONT> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
