As you've described it using tomcat's JNDI resources, the driver has to
be in common/lib. If the application defines and manages it's own pool
separate from tomcat, then you could put it in the app's WEB-INF/lib
folder. This has everything to do with how the classloaders work.
Since tomcat and your webapp both have to have access to the driver when
using container managed connection pools, it has to be in common/lib.
--David
Scott McClanahan wrote:
We are about to start testing the jdbc connection pooling capabilities
within tomcat. I don't have any control over the application instead
perform only administrative duties. Between the developers and myself
we have done a good bit of research and mapped out a decent plan but
there is one unresolved dispute between us. The developer says that the
jar file containing the database driver should be published within the
web applications WEB-INF/lib folder while I say it should be in
$CATALINA_HOME/common/lib. Who is right and why?
We hoped to define the datasource as a Resource within a DefaultContext
element in the server.xml so it is available to all web applications.
Is this good practice? I'd like to know of some ways you folks have
done it too if you've got the time.
Also any gotchas to look out for with connection pooling would be
helpful from those who have actually done it. Thanks.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
