This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

The scheduling use case as described is supported, to the extent that it ever will be (Spring Batch needs something external to trigger a JobLauncher, like a shell script). The 'massively parallel' use case is possible to implement with 1.0, but isn't directly supported out of the box yet. (Actually there is more than one way to approach it. The easiest is to flush to some durable middleware on a chunk boundary.) I have some proof of concept code that I will be publishing shortly. I chose to implement it with Spring Integration, which makes it much easier, but any kind of durable middleware could be adapted to the same pattern natively as well.

Comment

In the Massively Parallel Batch Processing use case, it mentioned a class org.springframework.core.batch.support.provider.Pa rtioningInterceptor . But I cannot find this in 1.0.0-Final api. May I know if it is achieved by another ways?

Besides, I found that the use cases documentation at: http://static.springframework.org/sp...ses/index.html are very useful. But it seems contains some out-of-date details, which are still referring to mx versions things like ItemProvider. Could you help to fix the use case documentation to avoid the confusion?