Skip to content

Fix function misspelling in gateway documentation. #10060

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 30, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions src/reference/antora/modules/ROOT/pages/changes-6.4-6.5.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion src/reference/antora/modules/ROOT/pages/gateway.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Expand Down