Issue Details (XML | Word | Printable)

Key: BATCH-733
Type: Sub-task Sub-task
Status: Open Open
Priority: Critical Critical
Assignee: Dave Syer
Reporter: Lucas Ward
Votes: 0
Watchers: 0
Operations

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

Upgrade StepExecutionResourceProxy to be able to use values from job execution context.

Created: 17/Jul/08 01:51 PM   Updated: 07/Aug/08 09:03 AM
Component/s: None
Affects Version/s: 1.1.0
Fix Version/s: 2.0.0.M3

Time Tracking:
Original Estimate: 0.5d
Original Estimate - 0.5d
Remaining Estimate: 0.25d
Time Spent - 0.25d Remaining Estimate - 0.25d
Time Spent: 0.25d
Time Spent - 0.25d Remaining Estimate - 0.25d


 Description  « Hide
A common use case for the job level ExecutionContext was to allow a file that was generated from one step as output, to be used as input in another step. However, the StepExecutionResourceProxy can't pull values from the job level execution context, which would require the value to be moved over.

 All   Comments   Work Log   Change History   FishEye   Builds      Sort Order: Ascending order - Click to sort in descending order
Lucas Ward added a comment - 21/Jul/08 03:24 PM
Dave,

It seems like this issue should be resolved in the 1.1 branch as well? The primary use case for the Job level ExecutionContext was to use a file created in one step as the input for another step.

Dave Syer added a comment - 22/Jul/08 01:51 AM
I'm trying to pull something more comprehensive together for 2.0. 1.1 could have a bandaid just for the specific use case you mention, but there is an easy workaround using a delegating reader that is also a StepExecutionListener. If you want a bandaid in 1.1.1 can we open another issue?