The traditional problem with Resource Bundles is that they are loaded
through the class loader and the class loader _caches_ the result for ever.
This mean that it usually requires a web container restart to pick up a
change in the property files. (you can also do it as a class, but it is
rather cumbersome and seldom used)
I have not yet tried this myself, but it appears that there now is a
clearCache() method on the ResourceBundle to overcome this limitation,
making it much easier to trigger a reload from within your application.
Did you mention why you were looking for alternative ways to do this?
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Paul Holm
Sent: 5. februar 2013 22:35
Subject: Re: [WEB400] Web Application Internalization Best Practices
Thanks for the response. What specific changes in JDK 6 are you referring
to relative to resource bundles? Are you talking about The ability to store
the .PROPERTIES file on the classpath and override properties in the
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
As an Amazon Associate we earn from qualifying purchases.