Hello, I'm looking for an elegant and simple solution to something that I'm sure others have dealt with already. Don't want to reinvent the wheel so I thought might help to hear from others on how they're handling it.
We have many webapps that need access to some common (mostly static) data for doing validations or populating dropdowns, radio buttons, etc. Some examples are lists of operating companies, company locations and/or company holidays, etc. A long time ago, someone here coded a "utility" class with static methods. The static methods return values which are hardcoded in the code. This works OK as long as the data NEVER changes. If it does, we have to recompile the class and tell everyone to get the new copy of the class in their app. I thought a cleaner way would be to have a servlet that starts when the webapp starts. The servlet would look up the values in some database (or properties file(s)) and place the values in the app context. Initially, we thought about doing this at the time a user logs into the site but storing that info in everybody's session is inefficient. How have others dealt with this? Thanks for any feedback. David ----------------------------------------- The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
