How is the mapper in 3.2 different to that in previous versions of 3.x?
Article ID: KB0087892
Updated On:
| Products | Versions |
|---|---|
| TIBCO MessageBroker | - |
| Not Applicable | - |
Description
Resolution:
- MB 3.2 introduces the concepts of Structural Mapping and Value Mapping
- The output of the mapping in 3.2 is ONLY the mapped tree and not the complete tree.
- Filtering was previously associated with the repeating node in the input schema. In MB 3.2, the filters are associated with the structural mapping. So now you can have a single repeating node in the input schema mapped (structurally) to several repeating nodes in the output schema each with a different filter.
- MB 3.2 mappers allow the inclusion of MB built-in functions (e.g. trim()) in mapper filters
- Previously branch-to-branch mapping was not recursive. In MB 3.2, it is.
- MB 3.2 mappers now support Unions
- Addition of an increment counter in the mapper
- Default values in the repository are now supported
- Addition of a root node
- MB 3.2 introduces the concepts of Structural Mapping and Value Mapping
- The output of the mapping in 3.2 is ONLY the mapped tree and not the complete tree.
- Filtering was previously associated with the repeating node in the input schema. In MB 3.2, the filters are associated with the structural mapping. So now you can have a single repeating node in the input schema mapped (structurally) to several repeating nodes in the output schema each with a different filter.
- MB 3.2 mappers allow the inclusion of MB built-in functions (e.g. trim()) in mapper filters
- Previously branch-to-branch mapping was not recursive. In MB 3.2, it is.
- MB 3.2 mappers now support Unions
- Addition of an increment counter in the mapper
- Default values in the repository are now supported
- Addition of a root node
Issue/Introduction
How is the mapper in 3.2 different to that in previous versions of 3.x?
Environment
Product: TIBCO MessageBroker
Version: 3.2.1.6, 3.1.7
OS: All
--------------------
Feedback
Yes
No
Powered by
