RE: Properties Files vs. War/Ear files

I don't know if this is considered kosher, but I put those properties in a 
predetermined location outside the web application.

PC2 

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On 
Behalf Of Walden H. Leverich
Sent: November 1, 2005 09:01
To: Java Programming on and around the iSeries / AS400
Subject: Properties Files vs. War/Ear files

All,
 
If I understand the concept correctly, one should put their "softcoded"
things into a properties file. This could be connection strings (if you're not 
using WebSphere data sources), Web Services addresses, URLs you access that are 
different between test and production, etc.
 
Now, the properties file is "wrapped" into the WAR file that's deployed to 
websphere. So, once deployed you go into the properties file and make your 
changes? Am I good so far? If so, what's the process for deploying updates? If 
I re-deploy the WAR file then I'll overwrite the properties file, so I have to 
make my changes again? 
 
Is there a way to exclude the properties file from the WAR and have WS leave it 
on the server?