Issue Details (XML | Word | Printable)

Key: BATCH-385
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Dave Syer
Reporter: Dave Syer
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Spring Batch

Merge user attributes in StepContext with ExecutionContext

Created: 26/Feb/08 02:13 AM   Updated: 07/Aug/08 10:06 AM
Component/s: Core
Affects Version/s: 1.0.0.m4
Fix Version/s: 1.0.0.m5

Time Tracking:
Not Specified


 Description  « Hide
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.

 All   Comments   Work Log   Change History   FishEye   Builds      Sort Order: Ascending order - Click to sort in descending order
Dave Syer added a comment - 29/Feb/08 05:33 AM
We decided not to merge them, but StepContext is dying anyway (still TODO).

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.

Dave Syer added a comment - 29/Feb/08 06:25 AM
StepScope is dead in favour of explicit listener registration. TODO: remove unnecessary delegate calls in ItemStreams.

Dave Syer added a comment - 29/Feb/08 07:28 AM
Finished.

Dave Syer added a comment - 07/Aug/08 10:06 AM
Assume closed as resolved and released