Oracle JHeadstart Developer's Guide - Downloads - Oracle

11.1. National Language Support in JHeadstart
JSF has built-in support for using property files or resource bundle classes as message
resource bundles. Message resource bundles can be used to make your application multilingual.
If you do not have internationalization requirements, it is still useful to use
message resource bundles to store “hard coded” text strings in a central place, where
they can be easily found and maintained.
When generating your application, JHeadstart generates a resource bundle that holds
translatable text. The name of the resource bundle can be specified in the Service-level
property NLS Resource Bundle. Using the Resource Bundle Type property you can
specify whether the resource bundle is generated as a property file, a java class or a
database table.
A property file is easiest to maintain by developers, it is a simple text file with key-value
pairs. However, a property file does not handle special symbols well. A Java-based
resource bundle is better suited for this. If you want the page text to be maintained or
translated by a super user or system administrator, then using a database table as
resource bundle is the best choice. See section Using Resource Bundle Type Database
Table for more information.
Button labels, page header titles, and other fixed “boilerplate text” generated by
JHeadstart are always generated into the resource bundle. However, if your application
should be truly multi-lingual, meaning that the generated pages cannot contain
hardcoded text at all, you should check the checkbox Generate NLS-enabled prompts
and tabs as well. When checked, the prompts, tab names and display titles that you
specify in the Application Definition Editor will also be generated into the resource
bundle.
In the Generator Default Locale property, you specify the locale that should be used to
populate the default resource bundle, which is the bundle that does not have the locale
suffixed to the name, for example ApplicationResources.properties. This
resource bundle is used when the user’s browser is set to a locale that is not supported
by your application.
In the Generator Locales property, you can optionally specify all other locales that must
be supported by your application as a comma delimited list. For each locale in this
property JHeadstart generates a resource bundle with the name as specified in the NLS
Resource Bundle property, suffixed with the locale code, for example
11 - 2 Internationalization JHeadstart Developer’s Guide