serializer
Icon |
|
|---|---|
Use When |
An entity message needs to be automatically formatted to JSON or XML |
Samples |
Format a model object to JSON prior to sending to a link:http-response(Http Response) for a web service |
Description |
Formats entity messages based on the input model |
Inbound Message Type |
Model Based Message |
Output Message Type |
Text Based Message |
Control Message Handling |
Input: When a unit of work boundary is received and 'Run When' is 'PER UNIT OF WORK' start the processing of this component or when any non-control message is received and 'Run When' is 'PER MESSAGE'. Output: A single control message will be forwarded to downstream components once all messages have been processed through this step. |
| Name | Description |
|---|---|
Whether to forward failed messages and continue processing. This is the name of a linked component to forward the failed messages to. |
|
Format |
Can have values of AUTOMATIC, JSON or XML. Default is AUTOMATIC. If AUTOMATIC is chosen, then the serializer will attempt to look at the flow parameters to determine what format should be used. If an Http Request started the flow, then the Accept header, the Content-Type header and the format parameter will all be inspected in order to determine the type. |
Structure |
Options for how to format the document. Options are: BY_TABLE and BY_INBOUND_ROW |