The main interface providing access to batch operations. The batch client is the RepeatCallback, where a single item or record is processed. The batch behaviour, boundary conditions, transactions etc, are dealt with by the RepeatOperations in such as way that the client does not need to know about them. The client may have access to framework abstractions, like template data sources, but these should work the same whether they are in a batch or not. More...
Public Member Functions | |
| RepeatStatus | Iterate (RepeatCallback callback) |
| Execute the callback repeatedly, until a decision can be made to complete. The decision about how many times to execute or when to complete, and what to do in the case of an error is delegated to a CompletionPolicy. More... | |
Detailed Description
The main interface providing access to batch operations. The batch client is the RepeatCallback, where a single item or record is processed. The batch behaviour, boundary conditions, transactions etc, are dealt with by the RepeatOperations in such as way that the client does not need to know about them. The client may have access to framework abstractions, like template data sources, but these should work the same whether they are in a batch or not.
Member Function Documentation
| RepeatStatus Summer.Batch.Infrastructure.Repeat.IRepeatOperations.Iterate | ( | RepeatCallback | callback | ) |
Execute the callback repeatedly, until a decision can be made to complete. The decision about how many times to execute or when to complete, and what to do in the case of an error is delegated to a CompletionPolicy.
- Parameters
-
callback
- Returns
- Exceptions
-
RepeatException
Implemented in Summer.Batch.Infrastructure.Repeat.Support.RepeatTemplate.
The documentation for this interface was generated from the following file:
- Summer.Batch.Infrastructure/Repeat/IRepeatOperations.cs