From: | Dave Cramer <Dave(at)micro-automation(dot)net> |
---|---|
To: | GB Clark <postgres(at)vsservices(dot)com> |
Cc: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Datasource and tomcat, Postgresql 7.4, jkd1.4.1 -- |
Date: | 2003-02-12 03:40:41 |
Message-ID: | 1045021241.1027.300.camel@inspiron.cramers |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Servlet containers have very specific rules on object visibility
it depends on where you put the jar. if you put the jar in the context,
then the class won't even exist outside of the context.
when you say servlet, is this a servlet inside the context or out?
FWIW I gave up on tomcat in favour of jetty. No automatic class
reloading, but that's where tomcat gets complicated.
Dave
On Tue, 2003-02-11 at 22:12, GB Clark wrote:
> Hello,
>
> Well I got my problem solved by searching through the tomcat mailling lists...
>
> I had to include my database parameters INSIDE the context for my application. Can anyone tell
> me why this fixed my problem? Or is that where the database parameters should be anyway...
>
> If I wanted another servlet to use the same datasource would I have to duplicate the parameters
> everytime?
>
> Something does not seem right there...
>
> Thanks for all the help.
>
> GB
--
Dave Cramer <Dave(at)micro-automation(dot)net>
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2003-02-12 06:13:39 | Re: omitted line in errors.properties (7.3.2) |
Previous Message | GB Clark | 2003-02-12 03:12:19 | Re: Datasource and tomcat, Postgresql 7.4, jkd1.4.1 -- |