I can see how it can be beneficial in these ways: 1) The application does not have to be redeployed if changing existing labels. 2) Label descriptions can be modified in real time. 3) If there are multiple applications and common labels, they can be shared among the other applications.
If you only have one application, and it's relatively simple, having a database resource may be an "overkill". I guess if I were supporting such a thing, I would create some tables something like this: Table: Resource Columns: resource_sid : Unique identifier for record; autoincrementing # value label_name : Resource identifier label_text : Text to associate with label language_code : Coded value representing the language Composite key would be language_code + label_name. Table: Language Columns: language_sid : Unique identifier for record; autoincrementing # value language_code : Coded value representing the language (e.g. 0, 1, 2, ...) langauge_text : Text representing the coded value (e.g. English, Spanish, French, ...) You would then have to track a language code in your user web session and use this code when generating your views to pull out the desired language labels. -- View this message in context: http://old.nabble.com/i18n-database-backed-tp27569081p27579439.html Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
