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. Using the IntelliScript Editor
  7. XMap
  8. Libraries
  9. Schema Object
  10. Command Line Interface
  11. Scripts
  12. Parsers
  13. Script Ports
  14. Document Processors
  15. Formats
  16. Data Holders
  17. Anchors
  18. Transformers
  19. Actions
  20. Serializers
  21. Mappers
  22. Locators, Keys, and Indexing
  23. Streamers
  24. Validators, Notifications, and Failure Handling
  25. Validation Rules
  26. Custom Script Components

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