Closed
Description
As of v5.2, JobRepository and JobExplorer have similar/same methods with different signatures/names doing the same thing (ie duplicate implementations). Here are some examples:
| JobRepository | JobExplorer |
|---|---|
| findJobExecutions | getJobExecutions |
| getLastJobExecution | getLastJobExecution |
| getJobNames | getJobNames |
| getJobInstance | getJobInstance |
| findJobInstancesByName | findJobInstancesByJobName |
Maintaining duplicate implementations is obviously not ideal. Moreover, JobExplorer is designed to be a read-only version of JobRepository, therefore JobRepository can technically be an extension of JobExplorer.
Finally, this would also make the batch configuration easier for users as they would not need to configure an additional bean (the JobExplorer) once they configured a JobRepository, which is almost always needed anyway.