Do you use job scoped beans?

[fmbenhassine]

Do you use job scoped beans (ie @JobScope)? If yes, please elaborate on your use case by adding a comment with an example.

[benelog]

In most cases, it’s used to configure beans associated with JobParameters.

  @Bean
  @JobScope
  public HelloDate2Tasklet helloDate2Tasklet(
      @Value("#{jobParameters['helloDate']}") LocalDate date) {
    return new HelloDate2Tasklet(date);
  }

[fmbenhassine]

The tasklet you shared does not require to be job-scoped, step-scope is enough.

[benelog]

@fmbenhassine
I know that using @StepScope is possible solution. However, since this code deals with JobParameter, I thought the object creation lifecycle aligns more logically with @JobScope, so I have been using that. From a usability perspective, I agree that replacing it with @StepScope would not cause any problems.

[skazsi]

In a multistep batch we use job scoped beans if they are requiring some job parameters and the bean is used multiple steps. I think decommissioning the job scope would be very weird. However, that's true in our case, that we try to avoid the multistep batches with simpler design if possible. As a consequence, not very often we actually need the job scoped beans. I would say in around 95% percent we are fine with the step scope only. But what we would do in the remining 5%? I hope this helps.

[fmbenhassine]

Based on #5311 (reply in thread), I believe we found a valid use case for job-scope starting from v6.