You can forward messages that are written to the internal WebSphere® Application Server logs to other processes for display. Messages that are displayed on the administrative console, which can be running in a different location than the server process, can be localized using the late binding process. Late binding means that WebSphere Application Server does not localize messages when they are logged, but defers localization to the process that displays the message.
Every method that accepts messages localizes those messages. The mechanism for providing localized messages is the resource bundle support provided by the IBM® Developer Kit, Java™ Technology Edition. If you are not familiar with resource bundles as implemented by the Developer Kit, you can get more information from various texts, or by reading the API documentation for the java.util.ResourceBundle, java.util.ListResourceBundle and java.util.PropertyResourceBundle classes, as well as the java.text.MessageFormat class.
The PropertyResourceBundle class is the preferred mechanism to use.
To properly localize the message, the displaying process must have access to the resource bundle where the message text is stored. You must package the resource bundle separately from the application, and install it in a location where the viewing process can access it.
By default, the WebSphere Application Server runtime localizes all the messages when they are logged. This localization eliminates the need to pass a .jar file to the application, unless you need to localize in a different location. However, you can use the early binding technique to localize messages as they log. An application that uses early binding must localize the message before logging it. The application looks up the localized text in the resource bundle and formats the message. Use the early binding technique to package the application resource bundles with the application.
To create a resource bundle, perform the following steps.
You 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 example 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 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. WebSphere Application Server 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 that is 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.
In this information ... | IBM Redbooks, demos, education, and more(Index) |