Spring/spring-batch
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

BATCH-405: Reviewed migration guide. Mostly small changes, other than not saying the Database schema was normalized, since it's still not completely due to the job parameters and execution context tables.

Browse Source
This commit is contained in:
lucasward
2008-03-03 17:38:47 +00:00
parent baa1acdd05
commit 7ccae72cc3
2 changed files with 21 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

35
src/.project
View File

@@ -1,18 +1,17 @@
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>src</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
</buildSpec>
<natures>
</natures>
<linkedResources>
<link>
<name>pom.xml</name>
<type>1</type>
<locationURI>PARENT/pom.xml</locationURI>
</link>
</linkedResources>
</projectDescription>
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>src</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
<buildCommand>
<name>org.eclipse.jdt.core.javabuilder</name>
<arguments>
</arguments>
</buildCommand>
</buildSpec>
<natures>
<nature>org.eclipse.jdt.core.javanature</nature>
</natures>
</projectDescription>

8
src/site/apt/migration/1.0-m4-m5.apt
View File

@@ -7,13 +7,13 @@
Updating Spring Batch jobs from 1.0.0.m4 to 1.0.0.m5 framework
This is a description of what needed to be done to migrate the samples from m4 to the m5 release.
The following is a description of what is needed to migrate the samples from m4 to the m5 release.
* JOB CONFIGURATION
* Tasklet's role has changed - no longer called iteratively, dedicated for tasks that are not natural to split into read-write phases (e.g. calling stored procedure or system command). Readers and writers are now typically injected into (ItemOriented)Step. See Tasklet and TaskletStep javadoc for more details.
* Tasklet's role has changed - It is no longer called iteratively, but is now dedicated for tasks that are not natural to split into read-write phases (e.g. calling stored procedure or system command). Readers and writers are now typically injected into (ItemOriented)Step. See Tasklet and TaskletStep javadoc for more details.
* Step scope removed - lifecycle of readers and writers explicitly handled by Step - use Step's 'streams' property to register streams instead of using step scope.
* Step scope removed - lifecycle of readers and writers explicitly handled by Step.
* One applicaton context for job rather than parent container and child job context. CommandLineJobRunner requires only one xml file location.
@@ -43,7 +43,7 @@ Updating Spring Batch jobs from 1.0.0.m4 to 1.0.0.m5 framework
* StepInstance removed from domain model.
* Database schema normalized.
* Database schema updated.
* JobInstance identity is now given by Job and JobParameters pair - identical JobInstances with different IDs no longer allowed (see JobInstance javadoc for more details).