Configuration file abuse

Java transgression #2

For values that are deemed worthy of being placed into a “configuration file” e.g. config.xml or config.properties consider the nature and use of such a “configurable” value.

In a business world, when a value in the so-called config-file needs changing an application re-build and re-deploy is likely required. Therefore, it becomes no more advantageous than a class-level constant and defeats the implied intent of the value residing in the configuration file.

Consider using a database in concert with an administration tool that allows for values to be changed on-the-fly. This would reduce time and resources and improve “time-to-market”. In addition, such an approach would have the potential to prevent invalid values from being entered and thus inadvertently causing application failure.