
Originally Posted by
Dave Syer
"Registering threads with an application context" isn't really a Spring idiom, so I wonder what you had in mind there? Anyway, I would say that scheduling and background threads are not a concern of Spring Batch per se, but they are Spring Framework concerns (especially now that Spring 3.0 has native declarative scheduling). Spring Batch would come in when you wanted to implement the tasks on your threads, and you didn't say much about that, so it's hard to say if it's a good fit or not.