Howdy, >Is there a best practice for this? I would like to see all of my app >config stuff in one XML file......so when I deploy the app between >(dev --> staging --> production) it goes smoothly without having to >rewrite any classes.....
This is a common need. There are many approaches, some more elegant than others. You definitely don't want to have environment-specific settings/properties in source code. You want them in a configuration file. Personally, I like having Ant fill in the property values depending on the destination environment when deploying my app. I use the token filtering features in Ant to do this. Other people just like to have different pre-written configuration files per environment, e.g. myapp-dev.prop, myapp-test.prop. Yet other people have one big configuration file with a property naming scheme inside it that makes the property environment-specific, e.g. myLogDir.dev=... myLogDir.test=... myLogDir.propd=... And there are many other options as well... Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
