GH-2825: Fix 4.3 Doc rendering
Fixes https://github.com/spring-projects/spring-integration/issues/2825
This commit is contained in:
@@ -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).
|
||||
|
||||
====
|
||||
[source, java]
|
||||
----
|
||||
|
||||
|
||||
@@ -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.
|
||||
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 value is set on the underlying `JdbcTemplate`.
|
||||
Few developers will probably ever want to process update counts, thus the value defaults to `true`.
|
||||
|
||||
Reference in New Issue
Block a user