I am not sure that you saw that Jim is not talking about changes to your resources being expensive to do but rather access to your resources being expensive to do with the database idea. I apologize if this was clear to you, but you seem to be missing that.
Jack On Thu, 16 Dec 2004 11:34:16 +0100, Nicolas De Loof <[EMAIL PROTECTED]> wrote: > > Thank you for help, > > About using database for messages, I agree it requires chaching and a reload > strategy. A simple "reload every 10 > minutes" might allow changing messages without requirement to stop app or to > search for files on server. > > I'm taking a look at Spring ReloadableResourceBundleMessageSource (what's a > name !). It allows bundle reload and sharing > messages between JSTL an Spring aware classes by using ApplicationContext as > a MessageSource. > > Nico. > > > > > > > > > -----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] > > > > This message contains information that may be privileged or confidential and > is the property of the Capgemini Group. It is intended only for the person to > whom it is addressed. If you are not the intended recipient, you are not > authorized to read, print, retain, copy, disseminate, distribute, or use > this message or any part thereof. If you receive this message in error, > please notify the sender immediately and delete all copies of this message. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~ "You can't wake a person who is pretending to be asleep." ~Native Proverb~ "Each man is good in His sight. It is not necessary for eagles to be crows." ~Hunkesni (Sitting Bull), Hunkpapa Sioux~ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
