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

GH-2825: Fix 4.3 Doc rendering

Browse Source 
Fixes https://github.com/spring-projects/spring-integration/issues/2825
This commit is contained in:
Gary Russell
2019-03-20 14:37:47 -04:00
parent afa98c1aaa
commit 9d19f66e83
2 changed files with 0 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
src/reference/asciidoc/gateway.adoc
View File

@@ -514,7 +514,6 @@ In this scenario, it is expected that the downstream flow will return a `Complet
In the following scenario, the caller thread returns immediately with a `CompletableFuture<Invoice>`, which is completed when the downstream flow replies to the gateway (with an `Invoice` object). In the following scenario, the caller thread returns immediately with a `CompletableFuture<Invoice>`, which is completed when the downstream flow replies to the gateway (with an `Invoice` object).
====
[source, java] [source, java]
---- ----

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

@@ -789,8 +789,6 @@ _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. <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. 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 used database.
The value is set on the underlying `JdbcTemplate`. The value is set on the underlying `JdbcTemplate`.
Few developers will probably ever want to process update counts, thus the value defaults to `true`. Few developers will probably ever want to process update counts, thus the value defaults to `true`.