From 233c0d96394bd3eb90f0179d307d3002bb5828d8 Mon Sep 17 00:00:00 2001 From: Glenn Renfro Date: Fri, 30 May 2025 17:20:33 -0400 Subject: [PATCH] Fix function misspelling in gateway documentation. * Tweaked the 6.4-6.5 documentation. --- .../antora/modules/ROOT/pages/changes-6.4-6.5.adoc | 7 ++++--- src/reference/antora/modules/ROOT/pages/gateway.adoc | 2 +- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/src/reference/antora/modules/ROOT/pages/changes-6.4-6.5.adoc b/src/reference/antora/modules/ROOT/pages/changes-6.4-6.5.adoc index ce08aabf424..747f2b5132d 100644 --- a/src/reference/antora/modules/ROOT/pages/changes-6.4-6.5.adoc +++ b/src/reference/antora/modules/ROOT/pages/changes-6.4-6.5.adoc @@ -15,7 +15,8 @@ The `AbstractCorrelatingMessageHandler` does not throw an `IllegalArgumentExcept Instead, such a collection is wrapped into a single reply message. See xref:aggregator.adoc[Aggregator] for more information. -The `AbstractMessageChannel` beans now throw a special `MessageDispatchingException` when an attempt to send a message to not running application is done. +The `AbstractMessageChannel` beans now throw a special `MessageDispatchingException` when an attempt is made to send a message to an application that is not running. + In general, it is a design error to try to produce a message from `afterPropertiesSet()`, `@PostConstruct` or bean definition methods. The `SmartLifecycle.start()` is preferred way for this kind of logic, or better to do that via inbound channel adapters. @@ -82,8 +83,8 @@ See xref:hazelcast.adoc[Hazelcast Support] for more information. [[x6.5-jdbc-changes]] == JDBC Support -The `BeanPropertySqlParameterSourceFactory` uses now internally the `MapSqlParameterSource` if provided input is a `Map`. -Also, `JdbcMessageHandler` exposes a `usePayloadAsParameterSource` flag to allow to deal with parameter source only against message payload. +The `BeanPropertySqlParameterSourceFactory` now internally uses the `MapSqlParameterSource` if provided input is a `Map`. +Also, `JdbcMessageHandler` exposes a `usePayloadAsParameterSource` flag to allow working with parameter source only against message payload. That's where the mentioned `MapSqlParameterSource` comes useful for request messages with map payloads. See xref:jdbc.adoc[JDBC Support] for more information. diff --git a/src/reference/antora/modules/ROOT/pages/gateway.adoc b/src/reference/antora/modules/ROOT/pages/gateway.adoc index 0ae39562158..aeb1b9a5c6b 100644 --- a/src/reference/antora/modules/ROOT/pages/gateway.adoc +++ b/src/reference/antora/modules/ROOT/pages/gateway.adoc @@ -720,7 +720,7 @@ where such a gateway can be used in some service which deals with the `Flux` of @Autowired TestGateway testGateway; -public void hadnleFlux() { +public void handleFlux() { Flux.just("1", "2", "3", "4", "5") .map(Integer::parseInt) .flatMap(this.testGateway::multiply)