From 5d17b746a2d4ccbe0292385bcd6d4c26f5192521 Mon Sep 17 00:00:00 2001 From: dsyer Date: Thu, 16 Jul 2009 15:40:03 +0000 Subject: [PATCH] Update migration notes to clarify Spring 3.0 position --- src/site/apt/migration/2.0-highlights.apt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/site/apt/migration/2.0-highlights.apt b/src/site/apt/migration/2.0-highlights.apt index b2bf16f83..60399cf14 100644 --- a/src/site/apt/migration/2.0-highlights.apt +++ b/src/site/apt/migration/2.0-highlights.apt @@ -13,7 +13,7 @@ Spring Batch 2.0 Highlights The four main themes of the new release are - * Java 5 and Spring 3.0 + * Java 5 (mandatory) and Spring 3.0 (optional) * Non-sequential execution @@ -29,6 +29,8 @@ Spring Batch 2.0 Highlights As you may know, Spring 3.0 is going to be the first major release of Spring to target Java 5 exclusively (I'll leave it to Juergen and Arjen to clarify that in more detail). Now that Sun has put an "{{{http://java.dzone.com/articles/rip%E2%80%A6jdk-14}End of Service Life}}" stamp on the JDK 1.4 it seems appropriate, and there are some great new features on Spring 3.0 that we want to take advantage of. + Since Spring 3.0 took a little longer to release than we had initially hoped we did some work in 2.0.0 to provide the late binding features independent of Spring 3.0. The 2.0.0 and 2.0.1 releases of Spring Batch actually do not work with Spring 3.0, but 2.0.2 should. The expressions in step scoped beans will use the weaker, but very similar, expression language from Spring Batch instead of the full Spring EL. In a future release of Spring Batch we will be able to fully support Spring EL in late binding expressions. + ** Type Safety Most of the work in the 2.0.0.M1 release of Spring Batch went into converting the existing code to Java 5, taking advantage of generics and parameterised types wherever we could. This gives users of the framework a much nicer programming experience, allowing compile time checks for type safety and ultimately reducing maintenance costs for projects using Spring Batch. For instance the in the <<>>, one of the central interfaces and user extension points in Spring Batch, we now have a typesafe <<>> method: