Resource Bundles 

The first part of the internationalizing process is resourcing. This involves isolating the locale-specific resources of the source code into modules called ResourceBundle. Those modules can then be independently added to or removed from the application. For a portal application, all the locale-specific strings and objects are stored in a set of ResourceBundle packaged with the PAR file.

The name of the resource bundle is defined by the property ResourceBundleName of the profile of the portal component.

The rules to find the resource bundle are the rules defined by the Java programming language. For example, if the current default locale is en_US, the locale of the component is fr_CH and the resource bundle name is localization, the resource bundle lookup will search for the following classes in the order:

·        localization _fr_CH

·        localization _fr

·        localization _en_US

·        localization _en

·        localization

The Java implementation expects the resource bundles to be accessible by the Java class loading mechanisms. That is why, the localization properties must be packaged in a folder of the PAR file that can be accessed by the Java class loader.

Example

Example localization properties – it could be a JAR file in PORTAL-INF/private/lib or just a single file in the PORTAL-INF/private/classes directory.

<Portal Archive>   |   +-- META-INF   +-- MANIFEST.MF   +-- …   +-- PORTAL-INF   |   |   |   +-- private   |   |   +-- classes   |   |     +-- my_Bundle.properties   |   |     +-- my_Bundle_fr.properties