From e6f0f5c7551a7f5f0bdde0f06939858f36c70e78 Mon Sep 17 00:00:00 2001 From: Kajsa Anderson <319167+kajsa@users.noreply.github.com> Date: Mon, 27 Mar 2023 18:40:11 -0500 Subject: [PATCH] Update scalability.adoc Move commentary on xml configuration just below the configuration it's explaining, instead of having it in the middle of the Java configuration example. --- spring-batch-docs/src/main/asciidoc/scalability.adoc | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/spring-batch-docs/src/main/asciidoc/scalability.adoc b/spring-batch-docs/src/main/asciidoc/scalability.adoc index 763095cec3..4a387f8e5b 100644 --- a/spring-batch-docs/src/main/asciidoc/scalability.adoc +++ b/spring-batch-docs/src/main/asciidoc/scalability.adoc @@ -302,6 +302,11 @@ configuration: ---- +[role="xmlContent"] +Similar to the multi-threaded step's `throttle-limit` attribute, the `grid-size` +attribute prevents the task executor from being saturated with requests from a single +step. + [role="javaContent"] The following example shows the `PartitionStep` configuration when using Java configuration: @@ -320,11 +325,6 @@ public Step step1Manager() { } ---- -[role="xmlContent"] -Similar to the multi-threaded step's `throttle-limit` attribute, the `grid-size` -attribute prevents the task executor from being saturated with requests from a single -step. - [role="javaContent"] Similar to the multi-threaded step's `throttleLimit` method, the `gridSize` method prevents the task executor from being saturated with requests from a single