From 8b54277a340867678ae891384b0e0eca1edab827 Mon Sep 17 00:00:00 2001 From: Artem Bilan Date: Thu, 25 Oct 2018 15:09:03 -0400 Subject: [PATCH] Fix tautology in service-activator.adoc JIRA: https://jira.spring.io/browse/INT-2416 See https://github.com/spring-projects/spring-integration/pull/2611 --- src/reference/asciidoc/service-activator.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/reference/asciidoc/service-activator.adoc b/src/reference/asciidoc/service-activator.adoc index 05debb47f3..b0bcd255c1 100644 --- a/src/reference/asciidoc/service-activator.adoc +++ b/src/reference/asciidoc/service-activator.adoc @@ -175,4 +175,4 @@ However keep in mind that, unlike <>, for a Service A So, if your method parameter is a `Message` and you copy some, but not all, existing headers in your service method, they will reappear in the reply message. It is not a Service Activator responsibility to remove headers from a reply message and, pursuing the loosely-coupled principle, it is better to add a `HeaderFilter` in the integration flow. Alternatively, a Transformer can be used instead of a Service Activator but, in that case, when returning a full `Message` the method is completely responsible for the message, including copying request message headers (if needed). -It is important to ensure that important framework headers (e.g. `replyChannel`, `errorChannel`), if present, must be preserved. +You must ensure that important framework headers (e.g. `replyChannel`, `errorChannel`), if present, have to be preserved.