Localized Resource builder inputs - Portlet Factory v6.1.2

Portlet Factory, Version 6.1.2

Localized Resource builder inputs

This topic describes the inputs for the Localized Resource builder.

Table 1. Localized Resource builder inputs
Input name Description
Name Name for this builder call. The WebSphere Portlet Factory Designer displays this name in the builder call list.
Resource Bundle Name Enter the fully-qualified name of the property file or Java class that serves as the default Resource Bundle. Properties files or ResourceBundle Java classes must be on IBM® WebSphere Portlet Factory class path. During development, store your resource bundles in the WebSphere Portlet Factory WEB-INF/work/source directory.
For example, enter com.acme.LabelResources for the property file stored as WEB-INF/work/source/com/acme/LabelResources.properties
Language Select the ISO language code for the default language.

The Country and Language inputs determine the resource bundle to use based first on the language code (for example, _fr) followed by the country (for example, _CA).

When the application runs, the JVM loads the resource bundle according to the client's locale and language settings. You can also profile this value to override the resource bundle that gets automatically loaded at execution time.
Country Select an ISO country code for the default country.
The Country and Language inputs determine the resource bundle to use based first on the language code (for example, _fr) followed by the country (for example, _CA).
When the application runs, the JVM loads the resource bundle according to the client's locale and language settings. You can also profile this value to override the resource bundle that gets automatically loaded at execution time.
Custom Variable Names Enable this input when you have more than one Localized Resource builder in a model to allow the two variables created by each Localized Resource builder to have different names.
When enabled, this check box forces variables created by this builder to use the builder name as part of the names assigned to the variables created by the builder.
For example, the builder call name is used as the variable name (instead of LocaleData) for the variable that holds the localized text. The builder call name and an Info suffix are used as the name for the variable that holds information about the resource bundle.
Create Lookup Table Enable this input to add to the model a lookup table containing localized resource data.
This table is named buildernameLookupTable and all the correct settings to make a lookup table out of this data are established.
Data in this table can be accessed as in any lookup table for use elsewhere in the model.
Ensure Element Validity Use this input to determine how the builder handles invalid XML characters in key names (such as numbers).

Disable

Default. To force the builder to use the key names unchanged. If the key name is invalid, an exception is thrown when WebSphere Portlet Factory tries to parse the name.

Enable

To convert invalid characters in keys to underscore (_ ) characters.

Create GetTextForKey Method Enable to create a method that takes a key passed as an argument and returns a string. The method name has the format buildernameGetTextForKey.
You can specify this method in the Get Text Method input of the Breadcrumbs builder.

Parent topic: Localized Resource builder

Library | Support |

Input name	Description
Name	Name for this builder call. The WebSphere Portlet Factory Designer displays this name in the builder call list.
Resource Bundle Name	Enter the fully-qualified name of the property file or Java class that serves as the default Resource Bundle. Properties files or ResourceBundle Java classes must be on IBM® WebSphere Portlet Factory class path. During development, store your resource bundles in the WebSphere Portlet Factory WEB-INF/work/source directory. For example, enter com.acme.LabelResources for the property file stored as WEB-INF/work/source/com/acme/LabelResources.properties
Language	Select the ISO language code for the default language. The Country and Language inputs determine the resource bundle to use based first on the language code (for example, _fr) followed by the country (for example, _CA). When the application runs, the JVM loads the resource bundle according to the client's locale and language settings. You can also profile this value to override the resource bundle that gets automatically loaded at execution time.
Country	Select an ISO country code for the default country. The Country and Language inputs determine the resource bundle to use based first on the language code (for example, _fr) followed by the country (for example, _CA). When the application runs, the JVM loads the resource bundle according to the client's locale and language settings. You can also profile this value to override the resource bundle that gets automatically loaded at execution time.
Custom Variable Names	Enable this input when you have more than one Localized Resource builder in a model to allow the two variables created by each Localized Resource builder to have different names. When enabled, this check box forces variables created by this builder to use the builder name as part of the names assigned to the variables created by the builder. For example, the builder call name is used as the variable name (instead of LocaleData) for the variable that holds the localized text. The builder call name and an Info suffix are used as the name for the variable that holds information about the resource bundle.
Create Lookup Table	Enable this input to add to the model a lookup table containing localized resource data. This table is named buildernameLookupTable and all the correct settings to make a lookup table out of this data are established. Data in this table can be accessed as in any lookup table for use elsewhere in the model.
Ensure Element Validity	Use this input to determine how the builder handles invalid XML characters in key names (such as numbers). Disable Default. To force the builder to use the key names unchanged. If the key name is invalid, an exception is thrown when WebSphere Portlet Factory tries to parse the name. Enable To convert invalid characters in keys to underscore (_ ) characters.
Create GetTextForKey Method	Enable to create a method that takes a key passed as an argument and returns a string. The method name has the format buildernameGetTextForKey. You can specify this method in the Get Text Method input of the Breadcrumbs builder.