This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
As opposed to externalizing the message bundle, what I have done in the past is put a FileWatchDog on it, monitoring it for any changes. Admitidly I haven't doen this for JSF, so don't know how you would tell JSF about it. But it should be possible. I'll check it out and let you know.
Joined: Jun 11, 2002
This is not as easy as it might seem....
<f:loadBundle uses ResourceBundle to load the bundle. This is turn uses a cache. So each time you get to the page where you are referencing your resource bundle, you are in fact asking ResourceBundle to give you a new Bundle. ie
But, Resource bundle get the original properties file off its cache. There doesn't seem to be a workaround for this. I found a post that mentioned to access the cache and clear through reflection, and tried it but that didn't work for me. Maybe, with whatever you're doing, it works for you.