From 52d7737aeb499dd1005d82e3f1258daf35e1a8d3 Mon Sep 17 00:00:00 2001 From: Iwein Fuld Date: Wed, 25 Mar 2009 09:55:50 +0000 Subject: [PATCH] INT-590 some last minute polishings --- spring-integration-reference/src/file.xml | 2 +- spring-integration-reference/src/http.xml | 18 ++++++++---------- 2 files changed, 9 insertions(+), 11 deletions(-) diff --git a/spring-integration-reference/src/file.xml b/spring-integration-reference/src/file.xml index 2969126641..fb4f05f110 100644 --- a/spring-integration-reference/src/file.xml +++ b/spring-integration-reference/src/file.xml @@ -124,7 +124,7 @@ To make things easier you can configure the FileWritingMessageHandler as part of an outbound channel adapter using the namespace. - ]]> + ]]> If you have more elaborate requirements to the payload to file diff --git a/spring-integration-reference/src/http.xml b/spring-integration-reference/src/http.xml index 42d0b653fb..0bb6109de4 100644 --- a/spring-integration-reference/src/http.xml +++ b/spring-integration-reference/src/http.xml @@ -1,21 +1,20 @@ - Http Support + HTTP Support
Introduction - The Http support allows for the making of Http requests and the processing of inbound Http requests. Because HTTP is always - request repsonse even if all that is returned is a 200 status code the Http support consists of two gateway implementations - HttpInboundEndpoint and HttpOutboundEndpoint. + The HTTP support allows for the making of HTTP requests and the processing of inbound Http requests. Because interaction HTTP is always synchronous, even if all that is returned is a 200 status code the Http support consists of two gateway implementations + HttpInboundEndpoint and HttpOutboundEndpoint.
Http Inbound Gateway - To receive messages over http you need to use an HttpInboundGateway. In common with the HttpInvoker + To receive messages over http you need to use an HttpInboundEndpoint. In common with the HttpInvoker support the Http Inbound Gateway needs to be deployed within a servlet container. The easiest way to do this is to provide a servlet definition in web.xml, see for further details. Below is an example bean defintion for a simple HttpInboundEndpoint @@ -23,7 +22,7 @@ ]]> - The HttpInboundGateway accepts an instance of InboundRequestMapper which allows + The HttpInboundEndpoint accepts an instance of InboundRequestMapper which allows customisation of the mapping from HttpServletRequest to Message. If none is provided the an instance of DefaultInboundRequestMapper will be used. This encapsualtes a simple strategy, which for example will create a String message for a POST request where the content type starts with "text", see the Javadoc for @@ -33,7 +32,7 @@ In sending a response to the client there are a number of ways to customise the behaviour of the gateway. By default the gateway will simply acknowledge that the request was received by sending a 200 status code back. It is possible to customise this response by providing an implementation of the Spring MVC View which will be invoked with the created Message. - In the case that the gateway should expect a reply to the Message then setting the expectReply flag will cause + In the case that the gateway should expect a reply to the Message then setting the expectReply flag will cause the gateway to wait for a reponse Message before creating a Http response. Below is an example of a gateway configured to use a custom view and to wait for a response. It also shows how to customise the Http methods accepted by the gateway, which are POST and GET by default. @@ -59,7 +58,7 @@ Http Outbound Gateway - To configure the HttpOutboundGateway write a bean definition like this: + To configure the HttpOutboundEndpoint write a bean definition like this: ]]> @@ -94,8 +93,7 @@ By default the Http request will be made using an instance of SimpleH To configure an inbound http gateway which expects a response. - ]]> + ]]> To configure the outbound gateway you can use the namespace support as well. The following code snippet shows the different configuration options for an outbound Http gateway.