On Fri, 15 Mar 2002, Nikola Milutinovic wrote:
> Date: Fri, 15 Mar 2002 14:08:38 +0100
> From: Nikola Milutinovic <[EMAIL PROTECTED]>
> Reply-To: Tomcat Users List <[EMAIL PROTECTED]>
> To: Tomcat Users List <[EMAIL PROTECTED]>
> Subject: Re: jndi versus database connection pooling
>
> > I use the JNDI based connection pool with Postgres quite successfully.
> > You will need to have postgresql.jar in $CATALINA_HOME/common/lib, and a
> > server.xml configuration something like this:
>
> Finally, someone using PostgreSQL...
>
> > <Context path="/foo" ...>
>
> What about "automatically deployed contexts"? I usually set a virtual
> host, with it's "appbase", for automatic context deployment. If I define
> the auto-deploy context I will have it deployed twice - no exactly what
> I want.
>
In 4.0.x, automatically deployed contexts with no <Context> entry do not
have any resources assigned to match up the resource references.
Therefore, you must explicitly define such webapps in the server.xml file
to give them access to the corresponding JNDI resources.
In the HEAD branch (what will become 4.1), Tomcat supports the notion of a
separate "context descriptor file", which is an XML file that just
contains the <Context> element for a particular webapp, plus all of its
nested elements. This gives you the following options (in addition to the
auto-deploy support in 4.0):
* Put a context description file in the appBase
directory and that webapp will be auto-deployed
with its resource definitions.
* Use the /install command of the Manager webapp
to dynamically deploy a context description file
(and associated WAR or webapp directory).
You can see this in action with a nightly build of Tomcat 4 -- the Admin
and Manager webapps themselves are deployed in this way.
> Nix.
>
Craig
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
