The Oracle Commerce Platform uses the Java ResourceBundle inheritance rules. According to Java specifications, all internationalized ResourceBundles belong to a family of ResourceBundle subclasses that share the same basename. The following steps are followed to determine which ResourceBundle.properties file to instantiate.
The
getBundlemethod first looks for a class name that matches the request locale’sbasename,language,country, andvariant. For example, if the desired class isDynamoBundle_fr_FR_Unix, it first looks for this class.If no class is found with the specified
language,country, andvariantarguments, it proceeds to step 2.The
getBundlemethod looks for a class that matches the request locale’sbasename,language, andcountry, such asDynamoBundle_fr_FR.If no class is found with the specified
languageandcountryarguments, it proceeds to step 3.The
getBundlemethod looks for a class with a name that matches the request locale’sbasenameandlanguage, such asDynamoBundle_fr.If no class is found with the specified
languageargument, it proceeds to step 4.The
getBundlemethod then goes through steps 1-3 for the default locale, instead of the request locale. For example, if the default locale isen_US_UNIX, it looks for a class name in the following order:DynamoBundle_en_US_UNIX
DynamoBundle_en_US
DynamoBundle_enIf no class is found for the default locale, it proceeds to step 5.
The
getBundlemethod looks for a class with a name of the following format:basename, such asDynamoBundle. This class is used as a defaultResourceBundlethat can be used by any locale that is not supported by the web site.If no class is found for the specified
basename, a JavaMissingResourceExceptionis thrown.
