> -----Original Message----- > From: Nathan Coast [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 29, 2004 4:17 AM > To: Struts Users Mailing List > Subject: message resources in db > > > Hi, > > Has anyone developed message resources that pulls messages > from a db? I > have followed a few links that discuss this but can't find any code: > > http://wiki.apache.org/struts/StrutsMessageResourcesFromDatabase
This notion keeps popping up, and I keep wondering why. On the surface it seems okay, keep everything where it's easy to maintain... but in reality, you really don't buy anything with it. If you do it so you can dynamically change the values, then you slow down your page throughput quite painfully. So, of course you cache the data... which means it's not dynamic and you either provide a way to flush the cache (which you could do for a flat file as well, as Spring has apparently done). Then you have the apparent fact that by doing so you are now outside the Java provided i18n stuff, so you might be in a position of trying to maintain this code to keep up with what Java provides for you autmatically. So, you gain what? it's in a database? I'm curios as to what you're reasoning is to put these into a database, coz I'm looking for a good excuse to do it myself :) > > these docs mention > org.apache.struts.util.OJBMessageResourcesFactory but > I can't find this class anywhere. > > If there is a db implementation for message resources? I guess the > natural progression is a web-app gui for managing those > resources. Does > such a thing exist? > > cheers > Nathan > -- > Nathan Coast > Managing Director > Codeczar Ltd > mob : (852) 9049 5581 > tel : (852) 2834 8733 > fax : (852) 2834 8755 > web : http://www.codeczar.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
