From 8a4896729fef099ed79386f434f89edbefd506b1 Mon Sep 17 00:00:00 2001 From: abilan Date: Fri, 12 May 2023 15:48:08 -0400 Subject: [PATCH 1/2] GH-8014: Improve doc for Service Activator Fixes https://github.com/spring-projects/spring-integration/issues/8014 --- src/reference/asciidoc/service-activator.adoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/reference/asciidoc/service-activator.adoc b/src/reference/asciidoc/service-activator.adoc index 3b76c99878b..031a19853a9 100644 --- a/src/reference/asciidoc/service-activator.adoc +++ b/src/reference/asciidoc/service-activator.adoc @@ -7,6 +7,10 @@ Alternatively, an output-producing service may be located at the end of a proces This is the default behavior if no output channel is defined. As with most of the configuration options described here, the same behavior actually applies for most of the other components. +The service activator is essentially a generic endpoint for calling method on some object with an input message and its headers. +Its internal logic is based on a `MessageHandler` which can be any possible implementation for specific use-case, for example `DefaultMessageSplitter`, `AggregatingMessageHandler`, `SftpMessageHandler`, `JpaOutboundGateway` etc. +Therefore any outbound gateway and outbound channel adapter mentioned in this reference manual should be treated as a specific extension of this service activator endpoint: they all in the end call some object's method. + [[service-activator-namespace]] ==== Configuring Service Activator From fa3d0d618c8bddbca3e5afa99333504f83ba9c9d Mon Sep 17 00:00:00 2001 From: Artem Bilan Date: Mon, 15 May 2023 09:40:07 -0400 Subject: [PATCH 2/2] Fix language in Docs Co-authored-by: Gary Russell --- src/reference/asciidoc/service-activator.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/reference/asciidoc/service-activator.adoc b/src/reference/asciidoc/service-activator.adoc index 031a19853a9..37d30ee35f1 100644 --- a/src/reference/asciidoc/service-activator.adoc +++ b/src/reference/asciidoc/service-activator.adoc @@ -7,9 +7,9 @@ Alternatively, an output-producing service may be located at the end of a proces This is the default behavior if no output channel is defined. As with most of the configuration options described here, the same behavior actually applies for most of the other components. -The service activator is essentially a generic endpoint for calling method on some object with an input message and its headers. -Its internal logic is based on a `MessageHandler` which can be any possible implementation for specific use-case, for example `DefaultMessageSplitter`, `AggregatingMessageHandler`, `SftpMessageHandler`, `JpaOutboundGateway` etc. -Therefore any outbound gateway and outbound channel adapter mentioned in this reference manual should be treated as a specific extension of this service activator endpoint: they all in the end call some object's method. +The service activator is essentially a generic endpoint for calling a method on some object with an input message (payload and headers). +Its internal logic is based on a `MessageHandler` which can be any possible implementation for a specific use-case, for example `DefaultMessageSplitter`, `AggregatingMessageHandler`, `SftpMessageHandler`, `JpaOutboundGateway` etc. +Therefore, any outbound gateway and outbound channel adapter mentioned in this reference manual should be treated as a specific extension of this service activator endpoint; they all, in the end, call some object's method. [[service-activator-namespace]] ==== Configuring Service Activator