spring-projects / spring-projects/spring-batch
JobStep could use a Joblocator instead of a hard coded job reference [BATCH-1576]
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3k
- Forks
- 2.5k
- Avg merge
- 6d 53m
- Merged PRs (30d)
- 3
Description
Dave Syer opened BATCH-1576 and commented
JobStep could use a Joblocator instead of a hard coded job reference. This would be more flexible at runtume and allow for instance configuration of the job in a child context, but still discoverable in the parent. Would require a new namespace element <job name="..."/> instead of <job ref="..."/>.
Affects: 2.1.0
1 votes, 1 watchers
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how JobStep currently resolves its hard-coded job reference and how the job namespace element is parsed. The work is done when a name-based JobLocator configuration supports child-context job instances while retaining parent discovery, with the new form covered by relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100