Mendelson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 27, 2006 9:47 AM
To: Tomcat Users List; [EMAIL PROTECTED]
Subject: RE: [SPAM] RE: Best Practice for properties files
Richard,
Thanks for the suggestion. I appreciate the elegance of your ant targets to
create war files targeted for ea
ne 24, 2006 9:44 PM
To: 'Tomcat Users List'
Subject: [SPAM] RE: Best Practice for properties files
Paul, are you using the deployer application to deploy your app (e.g.
apache-tomcat-5.5.17-deployer)?
If so, then it is very easy to modify the build.xml to customize the
log4j.properties, app
ssage-
From: Paul Mendelson [mailto:[EMAIL PROTECTED]
Sent: Friday, June 23, 2006 9:46 AM
To: Tomcat Users List
Subject: Best Practice for properties files
I have a fairly normal application that I am deploying on a tomcat 5.5
server.
My application uses log4j for its internal logging and I h
We had a similar problem. We moved the properties files into the
common/classes/<> or
shared/classes/<>. This way the properties files can be
changed in a production system without redeployment.
>>> [EMAIL PROTECTED] 06/23/06 10:46 AM >>>
I have a fairly normal application that I am deployin
I have a fairly normal application that I am deploying on a tomcat 5.5
server.
My application uses log4j for its internal logging and I have a
log4j.properties file that I keep in web/WEB-INF/classes. I also have a
regular app.properties file that I keep in web/WEB-INF.
I deploy my application t
