From fea200997ae24484328e95a22ece954ddfd8e68d Mon Sep 17 00:00:00 2001 From: Oleg Zhurakousky Date: Fri, 15 Apr 2011 15:07:28 -0400 Subject: [PATCH] INT-1732 changed documentation to remove reference to the old behavior of the Transformer. Added comments to Migration Guide on SI Portal --- docs/src/reference/docbook/transformer.xml | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/src/reference/docbook/transformer.xml b/docs/src/reference/docbook/transformer.xml index f55924f6ac..4ce000e62d 100644 --- a/docs/src/reference/docbook/transformer.xml +++ b/docs/src/reference/docbook/transformer.xml @@ -62,9 +62,7 @@ the payload type of inbound Messages. It may also accept Message header values either individually or as a full map by using the @Header and @Headers parameter annotations respectively. The return value of the method can be any type. If the return value is itself a Message, that will be passed along to - the transformer's output channel. If the return type is a Map, and the original Message payload was - not a Map, the entries in that Map will be added to the Message headers of the original - Message (the keys must be Strings). + the transformer's output channel. As of Spring Integration 2.0, a Message Transformer's transformation method can no longer return null.