Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy

   e-docs.beasys.com   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Release Notes   |   Portal API

   Commerce Servers Home   |   WebLogic Portal Doc Home   |   Internationalization   |   Previous Topic   |   Next Topic   |   Contents

Internationalization

Contents

Overview

Properties Files

Static Text

Constructed Messages

Overview

The BEA WebLogic Portal™ Administration Tool is supported by JSP bean objects which employ Java internationalization standards in the practice of presenting error and status messages. These beans use a BEA utility object called MessageBundle in conjunction with text-based properties files to produce two types of locale-specific display text. The two types of text are:

• Static Text

• Constructed Messages

Properties Files

Properties files are located in two particular directories in the portal framework. The first set of properties files supports the Portal Administration Tool and are located in com/beasys/portal/admin/jspbeans/i18n.

The second set of properties files supports both the administration tool and the run-time portal end-user tools. This set is located in com/beasys/portal/jspbeans/i18n.

Each properties file that supports a particular bean includes the bean name and a 'properties' extension. For example, the properties file that supports the com.beasys.portal.admin.jspbeans.PortalJspBean bean resides in the i18n directory, and is called PortalJspBean.properties.

Static Text

The BEA WebLogic Portal uses the following convention when naming static text entries in the properties files:

propertyName.txt=propertyValue

For example: error.txt=Error Occurred.

A static text property is acquired from a loaded MessageBundle using the following method:

String messageBundle.getString(String propertyName)

For example: System.out.printin(messageBundle.getString("error.txt"));

For more information, see the Portal API Documentation.

Constructed Messages

The dynamic display text created by internationalization often depends on one or more variables, and the order of these variables in a text segment is locale-specific. In this case, the BEA WebLogic Portal provides a means for constructing message segments for display.

The portal uses the following convention when naming message entries in properties files:

propertyName.msg=propertyValue

For example:

fieldRequired.msg={0} is a required field.

A constructed message is acquired from a loaded MessageBundle using the following method:

String messageBundle.getMessage(Object[ ] args, String propertyName)

For example:

Object[ ] args={"ContentURL"};

System.out.println(args,"fieldRequired.msg");

For more information, see the Portal API Documentation.

Copyright © 2000 BEA Systems, Inc. All rights reserved.
Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.