-
Notifications
You must be signed in to change notification settings - Fork 2
Output Generators
This is the 3rd type of components you can add to the flow, the OutputGenerator.
Its signature looks pretty much like the ChangesValidator and the Enricher we seen before, so I won't bother giving a lengthy example this time.
The output generators are invoked at the end of the flow after the validators and they only operate on valid commands.
They run inside a transaction.
When the flow is built, it already contains a single DbCommandsOutputGenerator. This is the guy who performs the actual SQL queries to persist the entities.
At Kenshoo, we usually add a ChangeLogOutputGenerator to our flow which gives us an audit log (this class is not provided in the library because it is specific to Kenshoo).
Setting up an Entity Persistence
Query language
Building the Flow
- Adding Simple Validators
- State Consumers
- Adding a Custom Validator
- Enrichers
- Output Generators
- Customizing Flows
- Primary and Secondary Tables (detailed example)
- State Consumers and Relations (what can we fetch)
- Child Commands
- Cascade Delete