Chuck,
then the docs are quite misleading.
In the 5.5-docs
(http://tomcat.apache.org/tomcat-5.5-doc/class-loader-howto.html) is
said:
quote
n a J2SE 2 (that is, J2SE 1.2 or later) environment, class loaders are
arranged in a parent-child tree. Normally, when a class loader is
asked to load a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gregor,
Gregor Schneider wrote:
Chuck,
then the docs are quite misleading.
Nope. Read them again.
quote
When a request to load a class
from the web application's WebappX class loader is processed, this
class loader will look in the local
I am testing our webapp under tomcat 6 after being under tomcat 5.5.
I have moved the following file from 5.5. into 6. I have placed it in the
conf directory:
Context path=/mo docBase=mo debug=0 reloadable=true
crossContext=true
Resource name=jdbc/mo auth=Container
.
-Original Message-
From: Mark Shifman [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 16, 2007 1:31 PM
To: Tomcat Users List
Subject: Re: JDBC connection issue
I just upgraded from 5.5 to 6.0 without any problems. My webapp was
deployed as a war file
with the config.xml in the META-INF
I just upgraded from 5.5 to 6.0 without any problems. My webapp was
deployed as a war file
with the config.xml in the META-INF (the exact config for 5.5). The
deployment does the
correct thing with the config.xml.
Make sure your jdbc library is in the CATALINA_HOME/lib dir.
I also was
I'm not sure about Tomcat 6, but in Tomcat 5.x there's no such thing
as $CATALIN_HOME/lib. YOur JDBC-drivers should either be bundled with
your web-app (if that's the only one using them) or, if used both from
Tomcat and your webapp(s) to $CATALINA_HOME/common/lib
Coming to the context:
- Create
Right ... tomcat 6's version of common/lib/ is simply lib/
Location of the driver jars is not entirely as simple as either in your
webapp or on the container's lib directory. Like the Highlander (good
movie if you haven't seen it), there can be only one. If another webapp
is using it and
.
Shouldn't have messed with something that worked :(.
-Original Message-
From: David Smith [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 16, 2007 2:26 PM
To: Tomcat Users List
Subject: Re: JDBC connection issue
Right ... tomcat 6's version of common/lib/ is simply lib/
Location
I see, so things quite changed from 5 to 6, however:
When it comes to a Tomcat 5.x, it still goes that you put your jar
(i.e. a jdbc-driver)
EITHER
in $CATALINA_HOME/lib (when used from Tomcat AND other webapps)
OR
in $CATALINA_HOME/webapps/yourwebapp/WEB-INF/lib (when used by a
specific
I just checked the docs and the order in which classloaders are searched
hasn't changed from 5.5 - 6.0. Still have to be careful a specific
class is only found once in the classloader tree from the perspective of
the webapp.
--David
Gregor Schneider wrote:
I see, so things quite changed
From: Hehl, Thomas [mailto:[EMAIL PROTECTED]
Subject: RE: JDBC connection issue
Before, we would run multiple webapps and each had their own
context file that matched the webapps. Like for the one below,
we had one called mo.xml.
That's still true in Tomcat 6. However, the preferred
From: Gregor Schneider [mailto:[EMAIL PROTECTED]
Subject: Re: JDBC connection issue
That's the big difference, before the classloader was delegating
That's simply not true - the webapp classloader delegates ONLY if the
classes cannot be found in the webapps's WEB-INF/lib or WEB-INF/classes
12 matches
Mail list logo
