Re: JNDI Datasource vs JDBC (Tomcat deployment)
Re: JNDI Datasource vs JDBC (Tomcat deployment)
- Subject: Re: JNDI Datasource vs JDBC (Tomcat deployment)
- From: Chuck Hill <email@hidden>
- Date: Wed, 12 Nov 2008 16:41:41 -0800
Hi Peter,
On Nov 12, 2008, at 4:28 PM, Peter Newnam wrote:
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?
One connection per EOF stack. By default, WO apps have a single
stack, but you can create a pool of them and share them among
sessions. Project Wonder has an implementation of this. It can
dramatically increase memory usage (each stack has it own cache) so it
is not a solution for everyone. In general you will find that the
scaling architecture of WO is very different from that of J2EE apps.
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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