when java.util.List is used as beanType (each data item fed to jdbcItemWriter is a List), jdbcItemWriter tries to assign each element of the list to a insert-sql parameter. If the list size is greater than the number of sql parameters (i.e., some elements in the end of the list should not be used), jdbcItemWriter will still try to assign to a non-exist sql parameter, causing out-of-range exeption.

The commit that made the difference in jdbcItemWriter when handling java.util.List type data item:

https://github.com/jberet/jsr352/commit/7d4f04bd52c7030e34fb17c1f0f798dc0a3bc9b7

there a code block was added to skip determing insert sql parameters when java.util.List is used.