Jake,
thanks, this is a great answer and answers my question exactly. :)
Especially the META-INF/context.xml. was somthing that I must have
overlooked
Ron
On Mon, 2002-12-02 at 11:09, Jacob Kjome wrote:
Hi Ron,
That is referring to a context configuration file. You *always* need to
Evening
A question to grow my knowledge:)
On tomcat 4.1.12-LE-jdk14 deployment with java jsdk 1.4.1_01-b01 I have
installed the two missing jar files from commons (dbcp and pool) and
made the example from the documentation (/DBTest) work. Great work, well
written and very clear.
So my question.
Hi Ron,
That is referring to a context configuration file. You *always* need to
set up your DataSources through the proprietary server configuration. The
stuff in the web.xml only defines the interface. For instance, if you set
up DBCP specific stuff in the web.xml file, your app would be
Hi,
I had posted this question some time back and am posting just in case some
one may have just missed it.
I am trying to get a JNDI connection to a datasource. For this I defined my
datasource exactly as it is described in the Tomcat docs - define a resource
in WEB.XML and in SERVER.XML
At 01:34 PM 12/14/01 +, you wrote:
Hi,
I had posted this question some time back and am posting just in case some
one may have just missed it.
I am trying to get a JNDI connection to a datasource. For this I defined
my datasource exactly as it is described in the Tomcat docs - define a
Hi,
Thankyou for the mail.
my datasource is sitting on the local computer and I can connect with a
normal JDBC Connection. The same driver properties I use to create a
datasource in server.xml and it fails.
I thought it can be a problem like Tomcat failing if we have the servlet.jar
in
At 07:07 PM 12/14/01 +, you wrote:
Hi,
Thankyou for the mail.
my datasource is sitting on the local computer and I can connect with a
normal JDBC Connection. The same driver properties I use to create a
datasource in server.xml and it fails.
I thought it can be a problem like Tomcat
