I recently upgraded an old application using Spring Batch 2.2.0 to 3.0.5. I made the necessary changes to the DB tables and some minute code changes related to parameter APIs.
Now when I run the application it is working but if a step's exit status is FAILED the job's exist status is set to COMPLETED. This is causing issues as our application code treats this as a successful execution. I am getting around it by adding a code snippet in afterJob() where I check the stepExecution list and set the job exit status manually, but shouldn't the Spring Batch framework take care of the exit status?
Is there anything that I missed while upgrading?
Ref: http://docs.spring.io/spring-batch/reference/html/configureJob.html