http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/context.html
Anything in <Context></Context> can go in a file outside server.xml, in the Host's appBase. Tomcat will pick it up automatically.
You name the file app.xml, so if your webapp is myApp, you would put a file called myApp.xml in the Host's appBase, and the contents of that file would be the Context element.
The admin and manager Contexts/apps use this method, so every Tomcat install has an example.
John
Pitre, Russell wrote:
Which file is this? I'd like to read up on it....
"put application specifics in context configuration files."
Russ
-----Original Message-----
From: Jacob Kjome [mailto:[EMAIL PROTECTED] Sent: Monday, August 18, 2003 10:40 AM
To: Tomcat Users List
Subject: Re: War Development w/ JNDI Datasources
You can always specify it in a separate context configuration file.
Keep the server.xml generic and put application specifics in context configuration files.
Jake
At 08:47 AM 8/18/2003 -0500, you wrote:
Hi All,
We are currently developing an application and using CVS to manage our source code. Our goal is to be able to pull down the project off of CVS and with a single Ant target, get the application up and running on
a local install of Tomcat.
The problem that has risen is that our DataSources are specified in JNDI (the server.xml in the {CATALINA_HOME}/conf) and is not something that we can feasibly park in CVS.
Is there a way to get the DataSources specified without modifying the server.xml? Or, should we be making an ANT target that loads a second instance of tomcat using a project specific server.xml, much like what Cactus describes?
Many Thanks, Jacob
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
