Summer.Batch.Infrastructure.Repeat Namespace Reference

Namespaces

Classes

interface  ICompletionPolicy
 Interface for batch completion policies, to enable batch operations to strategise normal completion conditions. Stateful implementations of batch iterators should only update state using the update method. If you need custom behaviour consider extending an existing implementation or using the composite provided. More...
 
interface  IRepeatContext
 Base interface for context which controls the state and completion / termination of a batch step. A new context is created for each call to the IRepeatOperations. Within a batch callback code can communicate via the IAttributeAccessor interface. More...
 
interface  IRepeatListener
 Interface for listeners to the batch process. Implementers can provide enhance the behaviour of a batch in small cross-cutting modules. The framework provides callbacks at key points in the processing. More...
 
interface  IRepeatOperations
 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...
 
class  RepeatException
 Exception thrown when repeat issues occur. More...
 
class  RepeatStatus
 Enumeration of possible Repeat statuses (either "Continuable" or "Finished") More...
 

Functions

delegate RepeatStatus RepeatCallback (IRepeatContext context)
 NB : Refers to the RepeatCallback java interface, with single method (doInIteration) More...
 

Function Documentation

delegate RepeatStatus Summer.Batch.Infrastructure.Repeat.RepeatCallback ( IRepeatContext  context)

NB : Refers to the RepeatCallback java interface, with single method (doInIteration)

Implementations return true if they can continue processing - e.g. there is a data source that is not yet exhausted. Exceptions are not necessarily fatal - processing might continue depending on the Exception type and the implementation of the caller.

Parameters
contextthe current context passed in by the caller.
Returns
an RepeatStatus which is continuable if there is (or may be) more data to process.
Exceptions
Exception