I know right now there is no such thing as inter-step transactionality in Spring-Batch. I\'m developing a complex batch job, with many steps performing several actions in da
Finally I have found a way to do this. As said in the last edition you must invoke the job from a transactional method:
@Transactional(propagation=Propagation.REQUIRED)
It's important set the propagation level to required in this level. And set the job level propagation to "mandatory", achieving with this the job and steps add their transactions to the current one. Nevertheless, as Michael Lange wrote, it's important to consider the potential volume size you are managing, in order to avoid out-of-the-limit commits or rollbacks.