From 11366a4602493a599fde48af3ed2acddd77293f9 Mon Sep 17 00:00:00 2001 From: Mark Fisher Date: Wed, 20 Aug 2008 07:37:19 +0000 Subject: [PATCH] Fixed minor typos in XML configuration examples. --- spring-integration-reference/src/configuration.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/spring-integration-reference/src/configuration.xml b/spring-integration-reference/src/configuration.xml index d5ea859aba..650e608891 100644 --- a/spring-integration-reference/src/configuration.xml +++ b/spring-integration-reference/src/configuration.xml @@ -178,7 +178,7 @@ - + ]]> @@ -220,7 +220,7 @@ channel. To determine the reply channel, it will first check if the NEXT_TARGET header contains a non-null value, next it will check if an "output-channel" was provided in the endpoint configuration: <service-activator input-channel="exampleChannel" output-channel="replyChannel" - ref="somePojo" method="someMethod"/> + ref="somePojo" method="someMethod"/> If no "output-channel" is available, it will finally check the message header's RETURN_ADDRESS property. If that value is available, it will then check its type. If it is a MessageTarget, the reply message will be sent to that target. If it is a String, then the endpoint will @@ -234,7 +234,7 @@ "selector" attribute to the endpoint definition and reference an implementation of the MessageSelector interface. ]]> + selector="exampleSelector"/>]]> Another important configuration option for message endpoints is the inclusion of @@ -273,7 +273,7 @@ ref="someObject" method="someMethod" output-channel="replyChannel"> - +