anchor.diff:  					<batch:listener ref="skipListener" />
   					<batch:listener ref="writeListener" />
   				</batch:listeners>
  -			</batch:chunk>
  -			*
  +			</batch:chunk>			
   		</batch:tasklet>
   	</batch:step>
   	<batch:listeners>
  
positive.code: ----
  <batch:job id="studentsJob" restartable="true">
  	<batch:step id="step1">
  		<batch:tasklet transaction-manager="transactionManager">                
  			
  			<batch:chunk reader="xmlItemReader" writer="databaseItemWriter"
  				processor="itemProcessor" commit-interval="1" *skip-limit="2">
  				 <batch:streams>
  					<batch:stream ref="errorItemWriter"/>
  					<batch:stream ref="successItemWriter"/>
  
negative.code: 	</batch:listeners>
  </batch:job>
  ----
  
  There is a skip-limit attribute (value as number) which is checked on every skippable exception, and when the number is reached, the step fails.
  
  +
  NOTE: The batch:streams, batch:listeners and batch:skippable-exception-classes configuration elements are all related to the way that erroneous input records are handled.
  +
  