This content has been marked as final.
Show 3 replies
-
1. Re: dynamic messages properties
lvdberg Oct 6, 2010 11:51 AM (in response to tienlantri)Hi,
We needed such functionality because the messagesXX file need to be adapted for every new string and the server need to be restarted to be effective.
I've made an Application scoped bean which contains text and its translation. It basically does the same as the messages component, but I use a table to store the translations, which makes it more dynamic.
Leo
-
2. Re: dynamic messages properties
cash1981 Oct 8, 2010 6:19 AM (in response to tienlantri)Why cant you use
Messages.instance().get("someKey")
-
3. Re: dynamic messages properties
lvdberg Oct 8, 2010 6:28 AM (in response to tienlantri)Hi,
Seam uses the messagesXX.properties and other static files, which can't be changed dynamically. So if you need to translate a new string it is not really practical to restart your server, so the application understand the new string, hence my suggestion for a more dynamic translator.
Leo