Edgar P Dollin wrote:
There is another issue regarding connection pooling in struts vs connection pooling in the container. In struts the war file contains all the information the app needs to run. With container pooling (at least with tomcat and resin) you have to coordinate the container configuration with struts configuration. With a single container running multiple apps this is a bit of an issue.
Edgar
I have that same example. The war has JNDI.
How the connection pool is provided is of no issue for the war. It works great. You can just lean on J2EE and let it take you home.
.V
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
