RE: JNDI Datasource vs JDBC (Tomcat deployment)
RE: JNDI Datasource vs JDBC (Tomcat deployment)
- Subject: RE: JNDI Datasource vs JDBC (Tomcat deployment)
- From: Peter Newnam <email@hidden>
- Date: Thu, 13 Nov 2008 11:28:20 +1100
- Acceptlanguage: en-US
- Thread-topic: JNDI Datasource vs JDBC (Tomcat deployment)
Hi Tonny
Thanks for the input. I am a
WebObjects newbie coming from J2EE environments, still trying to “merge”
my existing J2EE knowledge with my limited WO knowledge. One of the
advantages of the JNDI data source I am keen to leverage is that the JNDI
connection can be setup on various environments (DEV, TEST, PROD) and there
will not be a need for property files with the JDBC connection properties.
So does that mean that WO, more
specifically EOF, makes a single connection to a database via JDBC and then
just queues requests (I guess mostly deletions/updates/non-cached requests)
using its own internal pooling mechanism?
Thank you.
|
_______________________________________________
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