Issue Details (XML | Word | Printable)

Key: BATCH-354
Type: Sub-task Sub-task
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Thomas Risberg
Reporter: Lucas Ward
Votes: 2
Watchers: 1
Operations

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

Create JPA ItemReader/Writer

Created: 11/Feb/08 11:54 AM   Updated: 23/Sep/08 07:10 PM
Component/s: Infrastructure
Affects Version/s: None
Fix Version/s: 2.0.0.M1

Time Tracking:
Original Estimate: 1d
Original Estimate - 1d
Remaining Estimate: 0d
Time Spent - 1.25d
Time Spent: 1.25d
Time Spent - 1.25d


 Description  « Hide
We already have hibernate versions, but there should likely be JPA ones as well. It begs the question of whether or not a Hibernate specific one adds any value though. The whole stateless/stateful session topic might be enough to keep it around, since I'm not sure JPA has the same abstraction (I would have to double check though)

 All   Comments   Work Log   Change History   FishEye   Related Builds      Sort Order: Ascending order - Click to sort in descending order
Wayne Lund added a comment - 12/Feb/08 08:05 PM
I saw the question in the forum on this topic. The issue of ORM in batch needs to be resolved because projects want it for generally valid reasons. I'm actually hoping that JPA will help us resolve the issue in a standard way but JPA seems to be implemented today with the use of a lot of vendor extensions.

Lucas Ward added a comment - 09/Apr/08 05:34 PM
I'm actually okay with moving this one off the plate of 1.1, we haven't seen a lot of requests for it other than one on the forum. Unless anyone has objects I vote to move it under 2.0 (and even potentially past that)

Dave Syer added a comment - 10/Apr/08 02:20 AM
AGreed. It would work better in 2.0 with full Java 5 support.