> -----Original Message----- > From: Derek Broughton [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 15, 2004 12:09 PM > To: Struts Users Mailing List > Subject: Re: Struts, JSTL and ResourceBundle > > > On Wednesday 15 December 2004 14:07, Jim Barrows wrote: > > > From: Nicolas De Loof [mailto:[EMAIL PROTECTED] > > > > My customer would like to be able to change i18n messages > > > easily (without requirement to redeploy webapp or edit files > > > in context/WEB-INF/classes/...) > > > > > The solution isn't to put the messages into a database. > That just means > > everything gets slowed down as you constantly make db changes. > > Maybe, though I'd expect that there wouldn't be "constant" changes.
Blech. Wrong thing to say. Everythign gets slowed down because you have to hit the DB everytime you want a message. Cacheing the data means your right back where you started from, or trying to refresh the cache on each change. > > > What you might want to do is cause all of the i18n bundles to > > reload themselves to pick up new bundles. Which seems to be somewhat > > difficult, but this link might provide some help: > > http://www.jguru.com/faq/view.jsp?EID=44221 > > Doing it the "right" way might be a real pain, but if you make > context/WEB-INF/classes/ApplicationResources.properties a > symlink to a file > they can access, and use 'reloadable="true" > allowLinking="true"' in the > <CONTEXT> tag I would think it would work. Ugly, but simple. So is the linke I provided. The problem seems to be that the resource bundles aren't really designed to be reloaded during application run. There is apparently a request for enhancement at sun to do this. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
