Example: Logging resource bundles by creating a properties file

We can create resource bundles in several ways. The best and easiest way is to create a properties file that supports a properties resource bundle. This sample shows how to create such a properties file.

 

Resource bundle sample

For this sample, four localizable messages are provided. The properties file is created and the key-value pairs are inserted. All the normal properties file conventions and rules apply to this file. In addition, the creator must be aware of other restrictions that are imposed on the values by the Java MessageFormat class. For example, apostrophes must be escaped or they cause a problem. Avoid the use of non-portable characters. WAS does not support the use of extended formatting conventions that the MessageFormat class supports, such as {1, date} or {0,number, integer}.

Assume that the base directory for the application that uses this resource bundle is baseDir and that this directory is in the class path. Assume that the properties file is stored in the subdirectory baseDir not in the class path (for example, baseDir/subDir1/subDir2/resources). To allow the messages file to resolve, the subDir1.subDir2.resources.DefaultMessage name is used to identify the property resource bundle and is passed to the message logger.

For this sample, the properties file is named DefaultMessages.properties.

# Contents of the DefaultMessages.properties file  
MSG_KEY_00=A message with no substitution parameters.  
MSG_KEY_01=A message with one substitution parameter: parm1={0}  
MSG_KEY_02=A message with two substitution parameters: parm1={0}, parm2 = {1}  
MSG_KEY_03=A message with three parameter: parm1={0}, parm2 = {1}, parm3={2} 

When the DefaultMessages.properties file is created, the file can be sent to a translation center where the localized versions are generated.

---

 

Related tasks

Create log resource bundles and message files