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

More JDBC, PDF doc fixes

Browse Source
This commit is contained in:
Gary Russell
2018-07-30 14:08:55 -04:00
parent af57aaebdb
commit 0604258087
2 changed files with 3 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/reference/asciidoc/dsl.adoc
View File

@@ -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 <<java-dsl-runtime-flows>> for more information.

4
src/reference/asciidoc/jdbc.adoc
View File

@@ -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_.