You can create resource bundles in several ways. The best and easiest way is to create a properties file that supports a PropertiesResourceBundle. This sample shows how to create such a properties file.
For this sample, four localizable messages are provided. The properties file is created and the key-value pairs inserted into it. All the normal properties files conventions and rules apply to this file. In addition, the creator must be aware of other restrictions imposed on the values by the Java MessageFormat class. For example, apostrophes must be "escaped" or they will cause a problem. Also avoid use of non-portable characters. WebSphere Application Server - Express does not support usage 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 sre not in the classpath. Assume that the properties file is stored in a subdirectory of baseDir that is not in the classpath (e.g. baseDir/subDir1/subDir2/resources). In order to allow the messages file to be resolved, the name subDir1.subDir2.resources.DefaultMessage is used to identify the PropertyResourceBundle and is passed to the message logger.
For this sample, the properties file is named DefaultMessages.properties.
# Contents of 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}
Once the file DefaultMessages.properties is created, the file can be sent to a translation center where the localized versions will be generated.