Transform Filter builder inputsAdded by IBM on June 28, 2011 | Version 1 (Original)
|This topic describes the inputs for the Transform Filter builder.
This topic describes the inputs for the Transform Filter builder.
- General input
- Data to Transform
- Source Schema
- Filter Options
- Class Generation
Table 1. General input
|Name||Required. Enter a name for this builder call. The WebSphere® Portlet Factory Designer displays this name in the builder call list. |
Data to Transform
Table 2. Data to Transform inputs
|Apply Transform To||Specify one of the following options to determine how the transform is to be applied to the data. |
Target Operation Results
The target operation is invoked and the transform operation is applied to the results. The data service that this builder creates has inputs that are passed through to the target operation.Target Operation Inputs
The transform operation is applied to the inputs of the data service that this builder creates. The target operation is invoked with the transformed inputs. The results of the created data service are passed through from the target operation.Variable/Reference
The data service that this builder creates has no inputs. It transforms the data provided by the variable, reference, or other data service that you indicate and returns the transformed results. The Source Data input is made available.
|Target Operation||Required. Specify the target data service to which the transform is applied. |
This input is available if the Apply Transform To input is set to either Target Operation Results or Target Operation Inputs.
|Source Data||Required. Specify either a variable, method, or a data service. |
|Preserve Source Data||Set this input to have the builder copy the source data before it begins the transform. Clear this input to allow the builder to overwrite the source data. Overwriting can improve performance. |
Table 3. Source Schema inputs
|Source Schema||Specify an existing schema type in the WebApp. |
This input is available if the Source Data input does not define a schema type. If the Apply Transform To input is set to Target Operation Inputs, this input defines the schema type for the inputs to the data service that this builder creates.
Table 4. Filter Options inputs
|Element to Filter||Required. Specify the element from the data specified in the Source Data input on which filtering is applied. |
|Remove Empty Parent Elements||Set this input to have empty parent nodes removed from the output data. This input is available only if the Element to Filter input contains multiple segments. For example, if you have as source data RowSet/Row/ColumnA, filter out (remove) something like a ColumnA from a Row element, and the Row contains no more ColumnA tags, the builder removes the Row tags, too. If you select only RowSet/Row to filter, then this input does not apply and is not available. |
|Filter Behavior||Specify whether the filter retains or removes elements that match. |
Retain Matching Elements
Keep elements that match in the output data. Remove Matching Elements
Discard elements that match so that they do not appear in the output data.
|Filter Specification||Specify one of the following options to determine the comparison algorithm. |
Specify Conditions Below
The comparison algorithm is obtained from your input. The Match Mode and Filter Conditions inputs are available. Inline Method
The comparison algorithm is obtained from an inline method body. The Filter Method Body input is available. Custom Method
The comparison algorithm is obtained from a method that you identify. The Custom Filter Method input is available.
|Match Mode||Specify whether any or all conditions supplied in the Filter Conditions input must match. |
Match Any Filter Condition
The transform occurs if any condition is true. Match All Filter Conditions
The transform occurs only if all conditions are true. This input is available if the Filter Specification input is set to Specify Below.
|Filter Conditions||This input is available if the Filter Specification input is set to Specify Conditions Below. Specify the following items to define the comparison algorithm. |
The XML child element to filter againstOperator
The relational operator to use for the comparison (for example, =
(the equals character). Click in the text area to display the pull-down list.
GT (greater than)
LT (less than)
GT= (greater than or equal to)
LT= (less than or equal to)
!= (not equals)
matches regex (matches regular expression)
The value to which the element is compared.Comparison Type
The basis for the comparison. Click in the text area to display the pull-down list.
- Case Sensitive String - lower case and upper case characters do not match
- Case Insensitive String - lower case and upper case characters match
- Number - treat elements as numeric strings
- Date - treat elements as calendar dates. In Date Format, specify the format to be used.
Specify the format of the date to be used. This input is applicable only if Date is selected under Comparison Type.
|Filter Method Body||Specify the body of a filter method that accepts a single IXml argument and returns a boolean value. |
This input is available if the Filter Specification input is set to Inline Method.
|Custom Filter Method||Specify the name of a method that accepts a single IXml argument and returns a boolean value. |
This input is available if the Filter Specification input is set to Custom Method.
Table 5. Class Generation input
|Generate LJO||This button is active if all required inputs are specified. Click to generate a Java™ class with the name of the builder and having methods based on the builder inputs. |
Parent topic: Transform Filter builder