The advantage of letting the container (Tomcat) setup a JNDI DataSource is abstraction. It abstracts out the source of data from the web application. You no longer have to configure somewhere within your web application the db connection, user, password, etc.
This allows you to have a development Tomcat container configured with a DataSource to a test db and your production system to have a DataSource to a production db. As long as each container creates the same JNDI name you can install the webapp and use it for development or production without any changes. Regards, Glenn michael wimmer wrote: > hi, > > I use protomatter (protomatter.sourceforge.net) for connection pooling > and for now it seems to work pretty well. However, in this group and in > the tomcat documentation, connection pooling seems always been mentioned > in relation to JNDI or tyrex. > > Could anybody provide me with some information about the difference in > these approaches and their relative merits and demerits? > > thanks, > > Michael > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
