Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

JNDI Datasource vs JDBC (Tomcat deployment)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

JNDI Datasource vs JDBC (Tomcat deployment)

Subject: JNDI Datasource vs JDBC (Tomcat deployment)
From: Peter Newnam <email@hidden>
Date: Tue, 11 Nov 2008 09:31:40 +1100
Acceptlanguage: en-US
Thread-topic: JNDI Datasource vs JDBC (Tomcat deployment)

Hi

Does anyone know what the advantages/disadvantages are for using a JNDI Datasource with a Jakarta Commons Database Connection Pool (DBCP) compared to letting WebObjects (or more specifically Project Wonder if it makes a difference in the way a JDBC connection or pooling is handled) handle the database connection?  The application will only ever be deployed in a Tomcat container.

Any use cases where the one would be a strong favourite over the other?

Many thanks.

Regards,
Peter Newnam
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

Follow-Ups:
- Re: JNDI Datasource vs JDBC (Tomcat deployment)
  - From: "Tonny Staunsbrink" <email@hidden>

Prev by Date: Re: EOQualifier wildcard problem
Next by Date: Re: EOQualifier wildcard problem
Previous by thread: Re: EOQualifier wildcard problem
Next by thread: Re: JNDI Datasource vs JDBC (Tomcat deployment)
Index(es):
- Date
- Thread