setArguments(null) on MethodInvoker no longer coerces null to Object[0] [SPR-16075]

[spring-projects-issues]

Andy Wilkinson opened SPR-16075 and commented

There's a regression in 4.3.12 caused by this change. Spring Batch 3.0.8 relies on the old behaviour and, as a result, a NullPointerException is now thrown:

java.lang.NullPointerException
	at org.springframework.util.MethodInvoker.prepare(MethodInvoker.java:163)
	at org.springframework.batch.item.adapter.AbstractMethodInvokingDelegator.doInvoke(AbstractMethodInvokingDelegator.java:108)
	at org.springframework.batch.item.adapter.AbstractMethodInvokingDelegator.invokeDelegateMethod(AbstractMethodInvokingDelegator.java:60)
	at org.springframework.batch.core.step.tasklet.MethodInvokingTaskletAdapter.execute(MethodInvokingTaskletAdapter.java:47)
	at org.springframework.batch.core.step.tasklet.StepHandlerAdapterTests.testMapResultWithNull(StepHandlerAdapterTests.java:66)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
(41 more lines...)

---

Affects: 4.3.12

Issue Links:

• RequestMapping method returning Future with null result causes NullPointerException [SPR-16072] #20621 RequestMapping method returning Future with null result causes NullPointerException
• Backport selected refinements from the nullability efforts in 5.0 [SPR-15656] #20215 Backport selected refinements from the nullability efforts in 5.0

Referenced from: commits 03be809, c29b6f5