From 06042580879d1e66ef22cbda6f640d13b1eabe32 Mon Sep 17 00:00:00 2001 From: Gary Russell Date: Mon, 30 Jul 2018 14:08:55 -0400 Subject: [PATCH] More JDBC, PDF doc fixes --- src/reference/asciidoc/dsl.adoc | 4 ++-- src/reference/asciidoc/jdbc.adoc | 4 +--- 2 files changed, 3 insertions(+), 5 deletions(-) diff --git a/src/reference/asciidoc/dsl.adoc b/src/reference/asciidoc/dsl.adoc index 3d38645454..e8c5bb0c4b 100644 --- a/src/reference/asciidoc/dsl.adoc +++ b/src/reference/asciidoc/dsl.adoc @@ -579,8 +579,8 @@ Only limitation is here, that this flow is started with named direct channel - ` And Lambda flow can't start from `MessageSource` or `MessageProducer`. Starting with _version 5.0.6_, the generated bean names for the components in an `IntegrationFlow` include the flow bean followed by a dot as a prefix. -For example the `ConsumerEndpointFactoryBean` for the `.transform("Hello "::concat)` in the sample above, will end up with te bean name like `lambdaFlow.org.springframework.integration.config.ConsumerEndpointFactoryBean#0`. -The `Transformer` implementation bean for that endpoint will have a bean name such as `lambdaFlow.org.springframework.integration.transformer.MethodInvokingTransformer#0`. +For example the `ConsumerEndpointFactoryBean` for the `.transform("Hello "::concat)` in the sample above, will end up with te bean name like `lambdaFlow.org.springframework.integration.config.` `ConsumerEndpointFactoryBean#0`. +The `Transformer` implementation bean for that endpoint will have a bean name such as `lambdaFlow.org.springframework.integration.transformer.` `MethodInvokingTransformer#0`. These generated bean names are prepended with the flow id prefix for purposes such as parsing logs or grouping components together in some analysis tool, as well as to avoid a race condition when we concurrently register integration flows at runtime. See <> for more information. diff --git a/src/reference/asciidoc/jdbc.adoc b/src/reference/asciidoc/jdbc.adoc index b2d174363e..233e1ee3ed 100644 --- a/src/reference/asciidoc/jdbc.adoc +++ b/src/reference/asciidoc/jdbc.adoc @@ -829,9 +829,7 @@ _Required_. <2> If this attribute is set to `true`, all results from a stored procedure call that do not have a corresponding `SqlOutParameter` declaration are bypassed. For example, stored procedures can return an update count value, even though your stored procedure declared only a single result parameter. -<3> If this attribute is set to `true`, then all results from a stored procedure call that don't have a corresponding `SqlOutParameter` declaration will be bypassed. -E.g. Stored Procedures may return an update count value, even though your Stored Procedure only declared a single result parameter. -The exact behavior depends on the used database. +The exact behavior depends on the database implementation. The value is set on the underlying `JdbcTemplate`. Few developers will probably ever want to process update counts, thus the value defaults to `true`. _Optional_.