[#BATCH-670] Upgrade to Java 5.0

Spring Batch

Upgrade to Java 5.0

Created: 18/Jun/08 10:23 AM Updated: 03/Jul/08 10:19 AM

Component/s:

Core, Infrastructure

Affects Version/s:

2.0.0

Fix Version/s:

2.0.0.RC1

Time Tracking:

Issue & Sub-Tasks

Issue Only

Original Estimate:

41.62d

Remaining Estimate:

22.88d

Time Spent:

17.75d

Issue Links:

Depends

This issue is depended on by:

~~BATCH-675~~ API Analysis

Sub-Tasks:

All

Open

~~Upgrade JobParameters and ExecutionContext for Java 5~~

Closed

Lucas Ward

100%

~~Upgrade samples to Java 5.0~~

Closed

Thomas Risberg

85%

Add new Java 5.0 features

Open

Thomas Risberg

~~Support Callable<ExitStatus>~~

Closed

Dave Syer

100%

~~Improve typesafety of ItemProvider/Processor paradigm~~

Closed

Lucas Ward

~~Create JPA ItemReader/Writer~~

Closed

Thomas Risberg

100%

~~Change all collections to use generics~~

Closed

Robert Kasanicky

100%

~~Upgrade unit tests to use Spring Test Java 5 features~~

Closed

Thomas Risberg

100%

~~Upgrade ItemWriter and implementations to use parameterized types~~

Closed

Lucas Ward

100%

10.

~~Upgrade ItemReaders to use Parameterized types~~

Closed

Robert Kasanicky

100%

11.

~~Fix EasyMock warnings in core~~

Closed

Lucas Ward

100%

12.

~~Fix EasyMock warnings in Samples~~

Closed

Thomas Risberg

100%

13.

~~Fix EasyMock warnings in Infrastructure~~

Closed

Robert Kasanicky

100%

14.

~~Fix EasyMock warnings in infrastructure tests~~

Closed

Dave Syer

100%

15.

~~Generify ExceptionClassifier and ExceptionClassifierSupport~~

Closed

Thomas Risberg

16.

~~Parametrise RetryCallback and related interfaces~~

Resolved

Dave Syer

100%

Description

« Hide

This issue covers the whole of migrating Spring Batch to Java 5.0, including migrating existing features, updating the samples, adding new features such as special annotations and documenting all the changes.

All

Comments

Work Log

Change History

FishEye

Related Builds

Sort Order:

[ Permlink | « Hide ]

Chris Beams added a comment - 21/Jun/08 04:49 PM

A ParameterizedFieldSetMapper<T> would seem to make sense during the move to Java 5. I suppose this comment can be generalized to: "Add parameterization/generics support throughout the API as appropriate".

[ Permlink | « Hide ]

Lucas Ward added a comment - 22/Jun/08 07:08 PM

I agree, and I think that will be one of many changes we make to the API for generics. It's covered more generically in ~~BATCH-671~~ though.