My end solution ended up being to modify
$CATALINA_ROOT/conf/context.xml and put the JNDI data source
definition there. While I agree that modifying global server files is
less than ideal it is by far the simplest solution: It's only one
resource element that has to be added, it requires no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason,
Jason Cipriani wrote:
My end solution ended up being to modify
$CATALINA_ROOT/conf/context.xml and put the JNDI data source
definition there.
Yikes! You should /definitely/ not do that. Doing so will make that JNDI
data source available
Hmm, well, there are no other web applications, the server is
dedicated to this one. If there *were* other web applications, they
would likely be using the same data source anyways -- and in that case
it's certainly handy to be able to set the data source for multiple
web apps by maintaining just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason,
Jason Cipriani wrote:
I'm developing with Eclipse but could configure custom build steps
with ant. This solution would remove most of the inconvenience, but I
would still have to make 4 separate WARs available for distribution.
Not *too*
Jason Cipriani [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
I'm using Tomcat 6.0.18 on Windows XP SP3, Windows Server 2003, and
Windows Vista (UAC disabled).
I have a web application with a lot of configuration options, all
currently stored as servlet initialization parameters
I'm using Tomcat 6.0.18 on Windows XP SP3, Windows Server 2003, and
Windows Vista (UAC disabled).
I have a web application with a lot of configuration options, all
currently stored as servlet initialization parameters in
WEB-INF/web.xml. The parameters are site specific and are different
for my
From: Jason Cipriani [mailto:[EMAIL PROTECTED]
Subject: Convenient web application configuration.
Is there a better place I can store site-specific
configuration options?
Read the doc:
http://tomcat.apache.org/tomcat-6.0-doc/config/context.html#Context%20Parameters
Is there some other way
://www.nabble.com/Convenient-web-application-configuration.-tp20244034p20252816.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED
From: br1 [mailto:[EMAIL PROTECTED]
Subject: Re: Convenient web application configuration.
The easiest way is to place Context and the different
Resource elements into each Tomcat's server.xml file.
Certainly not easiest by any definition of the term that I'm familiar with,
especially
On Thu, Oct 30, 2008 at 8:22 AM, Pid [EMAIL PROTECTED] wrote:
Is your build process automated, say with ant or maven?
If so, it should be a relatively simple one-off job to configure
multiple output war files from one codebase with several configurations.
I'm developing with Eclipse but could
Jason Cipriani wrote:
I have a web application with a lot of configuration options, all
currently stored as servlet initialization parameters in
WEB-INF/web.xml. The parameters are site specific and are different
for my development machine, the machines of the two other developers
working on
Hi,
Caldarale, Charles R wrote:
From: br1 [mailto:[EMAIL PROTECTED]
Subject: Re: Convenient web application configuration.
The easiest way is to place Context and the different
Resource elements into each Tomcat's server.xml file.
Certainly not easiest by any definition of the term
12 matches
Mail list logo
