Lookup Table builder inputs for the New XML data typeAdded by IBM on August 31, 2010 | Version 1 (Original)
|This topic describes the Lookup Table builder inputs if you select the Data Type input New XML Data.
This topic describes the Lookup Table builder inputs if you select the Data Type
input New XML Data
- General inputs
- Additional Data Definition
Table 1. General inputs
|Name ||Enter a name for this builder call. The WebSphere® Portlet Factory Designer displays this name in the builder call list.|
Note: The name must begin with a letter or an underscore and contain only letters, digits, and underscores. This restriction allows the builder to use the Name input to build additional WebApp artifacts that implement the core of this builder runtime functionality.
|Data Type || Select the type of data element you want to query. You can select: |
New XML Data
Choose this to specify Lookup table data explicitly as a builder input.
|New XML Data || This input is displayed when the New XML data type is enabled. |
Enter in this text entry area the XML code that defines the Lookup table data.
|Variable Type ||This input allows you to use data in a resource bundle.|
You can choose:
Value Tag and Label Tag
To use standard model data in this form.Resource Bundle Style
To use data in the form that the Localized Resource builder produces.
|Value Set ||This input is available when the Variable type is Resource Bundle Style. |
Use this input to specify a reference to an XML variable, a comma-delimited string, or a hard-coded comma delimited string.
This will be a set of values only. The lookup table will be built from this set of values. The resulting table will be in the order of the values specified.
|Value Tag ||Enter the name (or, in the case of an XML variable, the node name) of the column to use to represent the value element. |
Note: If your query returns more than two columns, use this input to explicitly name the value column.
|Label Tag ||Enter the name (or, in the case of an XML variable, the node name) of the column to use to represent the label element.|
Note: If your query returns more than two columns, use this input to explicitly name the label column.
|Refresh Interval (secs) ||Enter the time in seconds that Lookup Table builder data is to be retained in the cache. |
Entering a value here enables caching and improves performance. This is generally a good idea if a large enough value is used to prevent unnecessary cache refreshes. A value of 300 seconds is usually appropriate in most applications.
Additional Data Definition
Table 2. Additional Data Definition inputs
|Get Data From ||Identifies the source of data. You can choose: |
To get data from Additional Pairs table.XML Data
To get data from an XML type variable. This choice is useful if there is a default set of labels and values that should appear in a number of select lists.
|Additional XML Data ||This input is available when the Get Data From input is XML Data. Specify an indirect reference to the location where the XML data is located.|
|Additional Pairs ||Specify any additional label and value pairs to be included in the lookup table results. (You typically do this to allow development to proceed while the database is under construction.) |
A label to be included in the ResultSet.Value
A value to be included in the ResultSetCollision Resolution
This choice allows you to handle the situation that can occur if a value and label pair that you specify is identical to one already contained in the data. When this occurs, select Use Original Value to use the pair contained in the original data. Select Use this Value to use the pair that you specified in the table.
|Table Position ||Specifies the location of additional pairs that are in the XML output of this builder. The choices are: |
The default. Additional data pairs placed in front of existing pairs in the XML stream.In Back
Additional data pairs placed in back of existing pairs in the XML stream.
|Parent Tag ||Specify the name of an XML element used to contain additional pairs in the table. Default element name is <UserAddition>.|
Table 3. Filtering input
|Label/Value Filter Mode ||Specify how XML nodes are to be filtered. You typically do this if the rows in your XML are not identical in terms of label and value content. |
You can choose:
Use elements with both label and value elements
To use elements with sub-elements that match the chosen Label and Value inputs.None: use all elements
Use all the data.
Parent topic: Lookup Table builder inputs: wpf7