Issue Details (XML | Word | Printable)

Key: BATCH-386
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

Hibernate failure job relies on funky flush logic

Created: 26/Feb/08 06:05 AM   Updated: 07/Aug/08 10:06 AM
Component/s: Infrastructure
Affects Version/s: 1.0.0.m5
Fix Version/s: 1.0.0.m5

Time Tracking:
Not Specified


 Description  « Hide
Hibernate failure job relies on funky flush logic. This should be analysed at least to see if the ItemWriter.flush() contract really makes sense. The problem is the HibernateAwareItemWriter needs access to the processed items during a flush(), but they are stored in RepeatContext which isn't available in the call to ItemWriter.flush().

 All   Comments   Work Log   Change History   FishEye   Builds      Sort Order: Ascending order - Click to sort in descending order
Dave Syer added a comment - 04/Mar/08 01:29 AM
This was refactored already as part of BATCH-378. It's much more satisfactory now - only relies on transaction resources.

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