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.
We don't really provide any database ItemWriters, since there wouldn't be much value in doing so. (Unlike say, a file ItemWriter) You can easily create your own Dao (or ItemWriter) that takes advantage of Jdbc Batching. However, keep in mind that doing so can complicate error processing. To give an example, if you have a chunk of size 10, and the 5th record is bad, if you are using Jdbc batch to output them, you have no way of knowing the 5th record is bad, since all 10 were committed at once. You will receive one exception for all. This can be solved by rolling back the chunk, and processing each one at a time, which isn't too difficult, but please keep in mind that it does add an extra 'layer'.
BATCH-194 was more about the fact that hibernate wouldn't flush the cache until the transaction was committed. Therefore, they weren't able to catch the error within developer code, since it wasn't thrown until the framework tried to commit a transaction.
However, the solution of using an interceptor may still have value if using a jdbc batching output solution.