I guess its another issue, where to store the property file and what to store in a property file. Basically from, BMG and Ray, I think
global property file (server.cnf)
should store enviroment dependant configuration where moving from one platform to another certainly require modification. eg. firewall setting, global debug ON/OFF, database settings.
package property file (customised properties)
should store project and package based configuration where settings should maintain consistant across dev, qa and prod enviroment. eg. mapping constant, database name.
If package dependant property is store in global property file, such as mapping constant, it would not be update easily with package publishing, which might create a post-production update blind spot.
If enviroment dependant property is store in package property file, such as firewall setting, it would overwrite correct firewall setting on that machine, thus a migration blind spot.
By doing so, it makes depolyment easier yet maintain flexibilities. However, it does requirement planning.
Just my thought, cheerz
Terry
#Flow-and-Java-services#Integration-Server-and-ESB#webMethods