Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
spring-issuemaster opened this issue Oct 16, 2017 · 0 comments

Comments

Projects
None yet
2 participants
@spring-issuemaster
Copy link
Collaborator

commented Oct 16, 2017

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:

  • #20621 RequestMapping method returning Future with null result causes NullPointerException
  • #20215 Backport selected refinements from the nullability efforts in 5.0

Referenced from: commits 03be809, c29b6f5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.