Re: JNDI Datasource vs JDBC (Tomcat deployment)
Re: JNDI Datasource vs JDBC (Tomcat deployment)
- Subject: Re: JNDI Datasource vs JDBC (Tomcat deployment)
- From: "Tonny Staunsbrink" <email@hidden>
- Date: Wed, 12 Nov 2008 08:35:08 +0100
Can't quite see how that will work with webobjects (in it's out of the box state), in WO you a multiple threads (when concurrent request handling is enabled) which uses a a synchronized data store. That combined WO's request handler locking strategies makes WO single threaded in practice.
The servlet container philosophy is more along the lines that no thread should wait for data access, hence the connection pool. Making servlet containers truly multithreaded.
Even if EOF could use a connection pool, i don't think it would change anything the EO object store it self is synchronized (by NSLock), so only one connection would ever used at any given time.
Cheers
Tonny
On Mon, Nov 10, 2008 at 11:31 PM, Peter Newnam
<email@hidden> wrote:
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 mezz.dk@gmail.com
_______________________________________________
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