For JDBC if it's not pooled in a container, it would be of little use to any application. Specifically the tomcat docs do say that connection pool is provided right here : http://jakarta.apache.org/tomcat/tomcat-5.5-doc/jndi-datasource-examples-howto.html#Database%20Connection%20Pool%20(DBCP)%20Configurations
Just set it up according to the docs(with changes for your jdbc driver) and you're good to go. On Wed, 10 Nov 2004 23:30:08 -0000, Steve Kirk <[EMAIL PROTECTED]> wrote: > > No interest in my original post so I'll rephrase. > > Is every container-managed DataSource configured in TC (e.g. via server.xml > / context.xml) automatically made pooled using commons pooling? Or can > ordinary non-pooled connections be created too using this mechanism? > > > -----Original Message----- > > From: Steve Kirk [mailto:[EMAIL PROTECTED] > > Sent: Tuesday 09 November 2004 00:45 > > To: 'Tomcat Users List' > > Subject: Are all TC-managed DataSources pooled? > > > > The docs under 'JDBC Data Sources' at > > http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jndi-resources > > -howto.html > > say, "The J2EE Platform Specification requires J2EE > > Application Servers to > > make available a DataSource implementation (that is, a > > connection pool for > > JDBC connections)." > > > > Now, I'm *not* criticising the docs, I'm seeking > > clarification. I'm not > > sure whether this is saying that a JDBC DataSource has to be > > pooled? Or is > > instead saying that J2EE requires pooled JDBC connections, or > > maybe that > > J2EE requires connections via a DataSource? > > > > I didn't think that DataSources had to be pooled, based on > > what is says > > here: > > http://java.sun.com/j2se/1.4.2/docs/api/javax/sql/DataSource.html > > > > This might sound like nit picking, but the answer to this > > will help me help > > someone else on another thread. Thanks. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
