Oracle JHeadstart Developer's Guide - Downloads - Oracle

11.3. Runtime Implementation of National Language Support
If you want to access a resource bundle in a JSF JSP page, you normally add a
loadBundle tag to your page like this:
And then you can access entries in this resource bundle like this:
While this is a simple technique, the drawback is that you explicitly have to name your
resource bundles in your page, and if you have multiple resource bundles, you need to
include multiple tags, and you need to know which entry resides in
which bundle.
JHeadstart takes a slightly different approach. Instead of generating
tags into the pages, JHeadstart generates a managed bean definition under the key nls
which instantiates a class that provides access to all resource bundles of your application.
In generated pages, you will often see references to this nls managed bean like this:
This approach provides you with the flexibility to (re-)organize your resource bundles as
you like, without the need to change the references to resource bundle entries in your
page.
In addition, this approach allows you to override JHeadstart and/or ADF Business
Components messages. To do so, simply include the message key, for example JHS-
00100 or JBO-27014 in one of your application resource bundles. If the key is not found in
your default resource bundle(s), the standard JHeadstart or ADF BC message bundles
are used.
To make this all work, the following managed bean definitions are generated into the
JhsCommon-beans.xml:
11 - 10 Internationalization JHeadstart Developer’s Guide