Skip to content

Commit 8020331

Browse files
committed
Clarify reference to example about job parameters in documentation
Resolves #4791
1 parent 17bc8f7 commit 8020331

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

spring-batch-docs/modules/ROOT/pages/domain.adoc

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -140,12 +140,12 @@ following image shows:
140140
.Job Parameters
141141
image::job-stereotypes-parameters.png[Job Parameters, scaledwidth="60%"]
142142

143-
In the preceding example, where there are two instances, one for January 1st and another
144-
for January 2nd, there is really only one `Job`, but it has two `JobParameter` objects:
145-
one that was started with a job parameter of 01-01-2017 and another that was started with
146-
a parameter of 01-02-2017. Thus, the contract can be defined as: `JobInstance` = `Job`
147-
+ identifying `JobParameters`. This allows a developer to effectively control how a
148-
`JobInstance` is defined, since they control what parameters are passed in.
143+
In the example from the xref:domain.adoc#jobinstance[Job Instance] section, where there are
144+
two instances, one for January 1st and another for January 2nd, there is really only one `Job`,
145+
but it has two `JobParameter` objects: one that was started with a job parameter of 01-01-2017
146+
and another that was started with a parameter of 01-02-2017. Thus, the contract can be defined
147+
as: `JobInstance` = `Job` + identifying `JobParameters`. This allows a developer to effectively
148+
control how a `JobInstance` is defined, since they control what parameters are passed in.
149149

150150
NOTE: Not all job parameters are required to contribute to the identification of a
151151
`JobInstance`. By default, they do so. However, the framework also allows the submission

0 commit comments

Comments
 (0)