> 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.
This was discussed, briefly, a few months ago. It would be very easy to extend the MessageResources classes in Struts to read from a database instead of properties file. All you need to do is extent PropertyMessageResources and overload the loadLocale() method. -TPP
<<winmail.dat>>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
