Has anybody given any thought to (much less actually done it) placing
properties files into the database and having the app server load/methods
call a persistent bean containing the keys/values? We are developing for
different clients using basically the same framework and I am thinking that
rather than maintain separate properties files in various physical
locations, to put the properties into the database, write a Java interface
defining the extraction methods, and implement concrete classes for each app
to load that app's properties.
Thoughts?
Mark
"If only I had known this ( T = ( - ? ))!"
