From ec6da02548994445f5fed0bae498bde17691783d Mon Sep 17 00:00:00 2001 From: Simonas Viliunas Date: Tue, 9 Jan 2018 21:33:42 +0200 Subject: [PATCH] Remove redundant full stops and fix broken list --- README.adoc | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/README.adoc b/README.adoc index 144c06924a..51899248c0 100644 --- a/README.adoc +++ b/README.adoc @@ -99,11 +99,12 @@ Break it down: ---- include::/complete/src/main/java/hello/BatchConfiguration.java[tag=readerwriterprocessor] ---- -. + The first chunk of code defines the input, processor, and output. -- `reader()` creates an `ItemReader`. It looks for a file called `sample-data.csv` and parses each line item with enough information to turn it into a `Person`. -- `processor()` creates an instance of our `PersonItemProcessor` you defined earlier, meant to uppercase the data. -- `write(DataSource)` creates an `ItemWriter`. This one is aimed at a JDBC destination and automatically gets a copy of the dataSource created by `@EnableBatchProcessing`. It includes the SQL statement needed to insert a single `Person` driven by Java bean properties. + +* `reader()` creates an `ItemReader`. It looks for a file called `sample-data.csv` and parses each line item with enough information to turn it into a `Person`. +* `processor()` creates an instance of our `PersonItemProcessor` you defined earlier, meant to uppercase the data. +* `write(DataSource)` creates an `ItemWriter`. This one is aimed at a JDBC destination and automatically gets a copy of the dataSource created by `@EnableBatchProcessing`. It includes the SQL statement needed to insert a single `Person` driven by Java bean properties. The next chunk focuses on the actual job configuration. @@ -112,7 +113,7 @@ The next chunk focuses on the actual job configuration. ---- include::/complete/src/main/java/hello/BatchConfiguration.java[tag=jobstep] ---- -. + The first method defines the job and the second one defines a single step. Jobs are built from steps, where each step can involve a reader, a processor, and a writer. In this job definition, you need an incrementer because jobs use a database to maintain execution state. You then list each step, of which this job has only one step. The job ends, and the Java API produces a perfectly configured job.