Table of Contents

Search

  1. Preface
  2. Introduction to Data Transformation
  3. Data Processor Transformation
  4. Wizard Input and Output Formats
  5. Relational Input and Output
  6. XMap
  7. Libraries
  8. Schema Object
  9. Command Line Interface
  10. Scripts
  11. Parsers
  12. Script Ports
  13. Document Processors
  14. Formats
  15. Data Holders
  16. Anchors
  17. Transformers
  18. Actions
  19. Serializers
  20. Mappers
  21. Locators, Keys, and Indexing
  22. Streamers
  23. Validators, Notifications, and Failure Handling
  24. Validation Rules
  25. Custom Script Components

Data Transformation User Guide

Data Transformation User Guide

Controlling How the Create Serializer Command Works

Controlling How the Create Serializer Command Works

When you run the
Create Serializer
command, the Developer tool converts the
Content
anchors of the Parser to
ContentSerializer
serialization anchors.
By default, the command converts all other text in the example source to
StringSerializer
serialization anchors. If the other text is boilerplate content, the output of the Serializer contains all the boilerplate that was in the original example source.
For example, suppose the Parser runs on tab-delimited source documents having the following structure:
Name (first and last):<tab>Ron Lehrer
Assume that the anchors are defined in the following way:
Source text
Anchor
Name
Marker
(first and last):<tab>
Not marked as an anchor
Ron Lehrer
Content
The XML output of the Parser is:
<FullName>Ron Lehrer<FullName>
Now, generate a Serializer from this Parser, and run the Serializer on the following input:
<FullName>Larissa Chan<FullName>
The output of the Serializer is:
Name (first and last):<tab>Larissa Chan