I've just started looking at Spring Batch as a possible replacement to our in-house batch framework. Actually creating a batch server with the capability to schedule Jobs and a JMX interface on top to provide an overview of running/previously ran job instances has taken little more than a day.
However, like Caoilte, I am finding problems with the documentation. The main one, and one which isn't in the documentation or the javadocs, is what tables are required by the JobRepository. The default is to have a database-persistence JobRepository, which is one of the requirements of my new server, but I cannot find any mention of the tables required. I've had to search Google high and low for any mention of them (If they are in the documentation, then I will gladly put salt on my humble pie).
I think actually creating a batch to run within Spring Batch is a rather complex task, given the vast array of configuration options available to you. This is a strength in my eyes. It provides opportunities to configure complex batch tasks in xml, which I have yet to find in any other batch framework (that I know of). But if you really did not want to harness the power of Spring Batch, why not just create a job with a single tasklet step (But then you have to ask yourself if its worth the overhead).
