Before you jump on the Spring Batch wagon, you may want to read what SO's own cletus has to say about its shortcomings:
http://www.cforcoding.com/2009/07/spring-batch-or-how-not-to-design-api.html.
I recently evaluated Spring Batch, and quickly rejected it once I realized that it added nothing to my project aside from bloat and overhead. Spring Batch may eventually become an OK product (much like EJBs got it right this time around), but at the moment it looks suspiciously like a solution in search of a problem.
