spring-projects / spring-projects/spring-batch
Make it illegal to specify a step listener that is narrower in scope than the <listener/> element [BATCH-1689]
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-1689 and commented
There are 3 types of listener in a step (whereas 2.1.0 only distinguishes one). It should be illegal to declare a listener of the wrong type in a wider scope than it applies. We should be able to declare <listeners/> at the chunk level for read/write/skip etc., but not step execution listeners.
Affects: 2.1.3
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 step and chunk-level declarations are parsed and validated in the Spring Batch configuration for the affected 2.1.3 behavior. Compare the three listener scopes described in the issue, and define done as rejecting step execution listeners declared in a wider scope while allowing applicable read, write, and skip listeners at chunk level.
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