On 10/03/2010 16:20, David kerber wrote:
As part of my migration from tc 5.5.x to 6.0.x, I'm reviewing my
deployment scripts, and noticed that in one of them, I'm deleting the
jdbc driver jar, jodbc.jar from the WEB-INF/lib folders, because it's
already on the system in jre/lib/ext.
However, I
Pid wrote:
On 10/03/2010 16:20, David kerber wrote:
As part of my migration from tc 5.5.x to 6.0.x, I'm reviewing my
deployment scripts, and noticed that in one of them, I'm deleting the
jdbc driver jar, jodbc.jar from the WEB-INF/lib folders, because it's
already on the system in jre/lib/ext.
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
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
From: David kerber [mailto:dcker...@verizon.net]
Subject: Re: Not getting an error that I though I should be getting
Could you clarify what a given branch of the classloader tree means?
There's a nice picture in the docs:
Bootstrap
|
System
|
Common
Caldarale, Charles R wrote:
From: David kerber [mailto:dcker...@verizon.net]
Subject: Re: Not getting an error that I though I should be getting
Could you clarify what a given branch of the classloader tree means?
There's a nice picture in the docs:
Bootstrap
|
System
