Uploaded image for project: 'Spring Framework'
  1. Spring Framework
  2. SPR-16075

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

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Complete
    • Affects Version/s: 4.3.12
    • Fix Version/s: 4.3.13
    • Component/s: Core
    • Labels:
    • Last commented by a User:
      true

      Description

      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...)
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                juergen.hoeller Juergen Hoeller
                Reporter:
                awilkinson Andy Wilkinson
                Last updater:
                Spring Issuemaster
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Days since last comment:
                  26 weeks, 3 days ago