diff --git a/src/docbkx/http.xml b/src/docbkx/http.xml index 855c3373f1..f363351cbb 100644 --- a/src/docbkx/http.xml +++ b/src/docbkx/http.xml @@ -74,21 +74,21 @@ To configure the HttpRequestExecutingMessageHandler write a bean definition like this: + ]]> - This bean definition will execute HTTP requests by first converting the message to an HTTP request using an instance of - DefaultOutboundRequestMapper. It will also expect to find the request URL in the message header under - the key HttpHeaders.REQUEST_URL. However, it is also possible to set a default URL as a constructor argument - along with other options as shown below. + This bean definition will execute HTTP requests by delegating to a RestTemplate. That template in turn delegates + to a list of HttpMessageConverters to generate the HTTP request body from the Message payload. You can configure those converters as well + as the ClientHttpRequestFactory instance to use: - - + + ]]> By default the HTTP request will be generated using an instance of SimpleClientHttpRequestFactory which uses the JDK HttpURLConnection. Use of the Apache Commons HTTP Client is also supported through the provided - CommonsClientHttpRequestFactory which can be injected into the outbound gateway. + CommonsClientHttpRequestFactory which can be injected as shown above. @@ -111,18 +111,28 @@ By default the HTTP request will be generated using an instance of Si 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. - ]]> - If you want to provide a custom OutboundRequestMapper, then a reference may be supplied to the - 'request-mapper' attribute. In that case however you will not be allowed to set the 'charset' - or 'extract-request-payload' attributes since those are both properties of the default - mapper (see the JavaDoc for DefaultOutboundRequestMapper for more information). + If your outbound adapter is to be used in a unidirectional way, then you can use an outbound-channel-adapter instead. This means that + a successful response will simply execute without sending any Messages to a reply channel. In the case of any non-successful response + status code, it will throw an exception. The configuration looks very similar to the gateway: + ]]> +