Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Why would you not store web application’s configuration variables simply in a class file?
I need to store variables like as how many product items to show in one page at a time. Where should I store them as such that my Java classes can use them? What is the standard for this?
That would require rebuilding, redeploying and restarting the whole beast whenever you make minor edits. It’s maybe not painful if you’re just locally hobbying. But in real world (when done rightly) you would need to get it through the whole chain of continuous build, automated testing, QA, etc. This makes no sense for a silly change in a configuration setting.
Your webapp must be designed that way that configuration can be changed externally and preferably also that it is able to reload configuration on demand (e.g. a button on an admin page) or even automatically (e.g. by
@Schedule @Singleton). This way the serveradmin has just to edit a simple and self-documenting textbased file instead of waiting hours or even days to get it into production.