You will likely want this to be a non-concurrent Quartz job, so that you don't have concurrent batch processing going on. Other then that, the Quartz job needs the job bean to run, and a job launcher. Those can be configured in your standard Spring Batch way in the resources.xml file in Grails.
Other notes:
- TaskExecutor configuration works great, and I would love to see GPars as a mechanism to define task executors for Spring Batch
- There were no issues using Groovy classes as implementors of ItemReader, ItemProcessor, or ItemWriter in Spring Batch
- There were no issues having Spring Batch beans, step scoped, injected with Grails managed beans
- Grails transaction manager did not appear to be picked up by Spring Batch, so I declared a ResourcelessTransactionManager
- Do not forget to use StepScope, so you can re-use other beans in your Grails configuration directly in your configured jobs, simply delcare with:
excellent post and blog in general
ReplyDeleteKiến thức của tác giả rất hay, cám ơn bạn đã chia sẻ.
ReplyDeletePage hữu ích : Bán đá thạch anh vụn
Mục post của anh khá được, anh đã chia sẻ.
ReplyDeleteXem thêm tại website: Vòng tay đá thạch anh
Bài viết của tác giả quá hữu ích, cám ơn bạn đã share.
ReplyDeleteXem tại website : Thiềm thừ
I have read your blog its very attractive and impressive. I like it your blog.
ReplyDeleteSpring online training Spring online training Spring Hibernate online training Spring Hibernate online training Java online training
spring training in chennai spring hibernate training in chennai