Registering Custom Localized
Static TextAny custom localized static text you create that is not loaded into the page using the
loadBundle
tag must be registered with the application using theresource-bundle
element in the application configuration resource file for your pages to have access to the text. Likewise, any custom error messages that are referenced by theconverterMessage
,requiredMessage
, orvalidatorMessage
attributes of an input component tag must also be made available to the application by way of theloadBundle
tag or theresource-bundle
element of the application configuration file.Here is the part of the file that registers some custom error messages for the Duke's Bookstore application:
<application> ... <resource-bundle> <base-name> com.sun.bookstore6.resources.CustomMessages </base-name> <var>customMessages</var> </resource-bundle> ... </application>Similarly to the
loadBundle
tag, the value of thebase-name
subelement specifies the fully-qualified class name of theResourceBundle
class, which in this case is located in theresources
package of the application.Also similarly to the
var
attribute of theloadBundle
tag, thevar
subelement of theresource-bundle
element is an alias to theResourceBundle
class. This alias is used by tags in the page to identify the resource bundle.The
locale-config
element shown in the previous section also applies to the messages and static text identified by theresource-bundle
element. As with resource bundles identified by themessage-bundle
element, make sure that the resource bundle identified by theresource-bundle
element actually contains the messages for the locales that you specify with theselocale-config
elements.To access the localized message, the page author uses a value expression to reference the key of the message from the resource bundle. See Performing Localization for more information.