Caldarale, Charles R wrote:
From: David kerber [mailto:dcker...@verizon.net]
Subject: Re: Not getting an error that I though I should be getting
Is it still considered good practice to put the jdbc driver jars into
the common lib location (catalina_home/lib on tc6)?
If Tomcat is managing the connection pool, it's required, not just good
practice. If your webapp is handling the connection pool, then the JDBC driver
jar should be in the webapp's WEB-INF/lib directory.
That's clear; thanks. My webapp is doing the pool management.
It sounds like you're saying that I'm probably ok with the way I'm set
up now, but if I change some things, it's possible that something may
come back to bite me in the future. Is that a correct interpretation?
That's unclear, since we don't have a good explanation of why you were getting
the errors on the previous level. It is dangerous to have the same classes
located in multiple places in a given branch of the classloader tree; all sorts
of subtle errors can occur.
Could you clarify what "a given branch of the classloader tree" means?
Are multiple webapps that have the same library jars in their
WEB-INF/lib considered to be the same branch? I didn't think so, but
considering your statement, now I'm not so sure. I've got my jdbc
driver jar (along with 5 or 6 others) in WEB-INF/lib for each webapp.
I'm not going to go back and try to create the errors I was getting a
few years ago which I was able to resolve by moving my jdbc driver jar
file around. So I guess I'll go with what works for now unless I find
another good reason to change it during my migration testing, since I'm
moving away from the version in which I got those errors.
D
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
