
|
If you were logged in you would be able to see more operations.
|
|
|
|
Developers find StepContext easy to locate and use, and mistakenly assume that its attributes ight be persisted (like the ExecutionContext). It's an easy mistake to make, so maybe user defined attributes in StepContext should use an ExecutionContext, or maybe a separate API in StepContext could provide the same feature.
|
|
Description
|
Developers find StepContext easy to locate and use, and mistakenly assume that its attributes ight be persisted (like the ExecutionContext). It's an easy mistake to make, so maybe user defined attributes in StepContext should use an ExecutionContext, or maybe a separate API in StepContext could provide the same feature. |
Show » |
|
Added an accessor for job parameters in StepExecution - make StepListener the best place to get hold of JobParameters.
Refactored existing StepContextAware to StepListener implementations. The BatchResourceFactoryBean is now a ProxyResource with a hint in docos and exception messages about registering with a step.