INT-3913 Remove/resolve deprecation from the past

JIRA: https://jira.spring.io/browse/INT-3913

* Remove deprecated classes and methods/constructors, deprecated XML attributes
* Remove `TcpConnectionEventListeningMessageProducer` and rework tests logic to the `ApplicationEventListeningMessageProducer`
* Fix several typos
* Remove/rework deprecated entities mentioning

src/reference/asciidoc/file.adoc

@@ -234,11 +234,7 @@ To prevent their use, you should configure your own filter (e.g. `AcceptAllFileL
 [[watch-service-directory-scanner]]
 ==== WatchServiceDirectoryScanner
 
-This scanner was added in _version 4.2_. It replaces the existing `RecursiveLeafOnlyDirectoryScanner` which is
-inefficient for large directory trees.
-The `FileReadingMessageSource.WatchServiceDirectoryScanner` requires Java 7 or above.
-
-This scanner relies on file system events when new files are added to the directory.
+The `FileReadingMessageSource.WatchServiceDirectoryScanner` relies on file system events when new files are added to the directory.
 During initialization, the directory is registered to generate events; the initial file list is also built.
 While walking the directory tree, any subdirectories encountered are also registered to generate events.
 On the first poll, the initial file list from walking the directory is returned.
@@ -254,9 +250,7 @@ In this case, the root directory is re-scanned completely.
 To avoid duplicates consider using an appropriate `FileListFilter` such as the `AcceptOnceFileListFilter` and/or
 remove files when processing is completed.
 
-Since _version 4.3_, the top level `WatchServiceDirectoryScanner` has been deprecated in favor of
-`FileReadingMessageSource` internal logic for the `WatchService`.
-Now this can be enable via `use-watch-service` option, which is mutually exclusive with the `scanner` option.
+The `WatchServiceDirectoryScanner` can be enable via `FileReadingMessageSource.use-watch-service` option, which is mutually exclusive with the `scanner` option.
 An internal `FileReadingMessageSource.WatchServiceDirectoryScanner` instance is populated for the provided `directory`.
 
 In addition, now the `WatchService` polling logic can track the `StandardWatchEventKinds.ENTRY_MODIFY` and

src/reference/asciidoc/ftp.adoc

@@ -720,9 +720,6 @@ if (closeable != null) {
 }
 ----
 
-Note: In previous releases the session was in the `file_remoteSession` header, but this is deprecated - use
-`closeableResource` instead.
-
 Framework components such as the <<file-splitter,File Splitter>> and <<stream-transformer,Stream Transformer>> will
 automatically close the session after the data is transferred.
 

src/reference/asciidoc/gateway.adoc

@@ -145,9 +145,6 @@ For example, if you wish to route on the simple method name, you might add a hea
 NOTE: The `java.reflect.Method` is not serializable; a header with expression `#gatewayMethod` will be lost if you later serialize the message.
 So, you may wish to use `#gatewayMethod.name` or `#gatewayMethod.toString()` in those cases; the `toString()` method provides a String representation of the method, including parameter and return types.
 
-NOTE: Prior to 3.0, the `#method` variable was available, representing the method name only.
-This is still available, but deprecated; use `#gatewayMethod.name` instead.
-
 Since 3.0, `<default-header/>` s can be defined to add headers to all messages produced by the gateway, regardless of the method invoked.
 Specific headers defined for a method take precedence over default headers.
 Specific headers defined for a method here will override any `@Header` annotations in the service interface.

src/reference/asciidoc/http.adoc

@@ -632,8 +632,6 @@ http://static.springsource.org/spring/docs/current/javadoc-api/org/springframewo
 
 http://static.springsource.org/spring/docs/current/javadoc-api/org/springframework/http/client/HttpComponentsClientHttpRequestFactory.html[HttpComponentsClientHttpRequestFactory] - Uses http://hc.apache.org/httpcomponents-client-ga/[Apache HttpComponents HttpClient] (Since Spring 3.1)
 
-http://static.springsource.org/spring/docs/current/javadoc-api/org/springframework/http/client/CommonsClientHttpRequestFactory.html[ClientHttpRequestFactory] - Uses http://hc.apache.org/httpclient-3.x/[Jakarta Commons HttpClient] (Deprecated as of Spring 3.1)
-
 If you don't explicitly configure the _request-factory_ or _rest-template_ attribute respectively, then a default RestTemplate which uses a `SimpleClientHttpRequestFactory` will be instantiated.
 
 [NOTE]

src/reference/asciidoc/ip.adoc

@@ -420,21 +420,7 @@ Configuring a connection interceptor factory chain.
 === TCP Connection Events
 
 Beginning with version 3.0, changes to `TcpConnection` s are reported by `TcpConnectionEvent` s.
-`TcpConnectionEvent` is a subclass of `ApplicationEvent` and thus can be received by any `ApplicationListener` defined in the `ApplicationContext`.
-
-[NOTE]
-=====
-The following is deprecated as of _version 4.2_; use the generic Event Inbound Channel Adapter instead.
-See <<appevent-inbound>>.
-
-For convenience, a `<int-ip:tcp-connection-event-inbound-channel-adapter/>` is provided.
-This adapter will receive all `TcpConnectionEvent` s (by default), and send them to its `channel`.
-The adapter accepts an `event-type` attribute, which is a list of class names for events that should be sent.
-This can be used if an application subclasses `TcpConnectionEvent` for some reason, and wishes to only receive those events.
-Omitting this attribute will mean that all `TcpConnectionEvent` s will be sent.
-You can also use this to limit which `TcpConnectionEvent` s you are interested in ( `TcpConnectionOpenEvent`, `TcpConnectionCloseEvent`, or `TcpConnectionExceptionEvent`).
-=====
-
+`TcpConnectionEvent` is a subclass of `ApplicationEvent` and thus can be received by any `ApplicationListener` defined in the `ApplicationContext`, for example <<appevent-inbound,Event Inbound Channel Adapter>>.
 
 `TcpConnectionEvents` have the following properties:
 

src/reference/asciidoc/jpa.adoc

@@ -144,7 +144,7 @@ Either this attribute or the _entity-manager_ attribute or the _jpa-operations_
 *entity-manager*
 
 The reference to the JPA Entity Manager that will be used by the component.
-Either this attribute or the _enity-manager-factory_ attribute or the _jpa-operations_ attribute must be provided.
+Either this attribute or the _entity-manager-factory_ attribute or the _jpa-operations_ attribute must be provided.
 
 NOTE: Usually your Spring Application Context only defines a JPA Entity Manager Factory and the EntityManager is injected using the @PersistenceContext annotation.
 This, however, is not applicable for the Spring Integration JPA components.

src/reference/asciidoc/sftp.adoc

@@ -809,9 +809,6 @@ if (closeable != null) {
 }
 ----
 
-Note: In previous releases the session was in the `file_remoteSession` header, but this is deprecated - use
-`closeableResource` instead.
-
 Framework components such as the <<file-splitter,File Splitter>> and <<stream-transformer,Stream Transformer>> will
 automatically close the session after the data is transferred.
 

src/reference/asciidoc/xml.adoc

@@ -814,7 +814,7 @@ If you need to extend beyond the capabilities of that default implementation, th
 [[xml-xpath-header-enricher]]
 === XPath Header Enricher
 
-The XPath Header Enricher defines a Header Enricher Message Transformer that evaluates XPath expressions against the message payload and inserts the result of the evaluation into a messsage header.
+The XPath Header Enricher defines a Header Enricher Message Transformer that evaluates XPath expressions against the message payload and inserts the result of the evaluation into a message header.
 
 Please see below for an overview of all available configuration parameters:
 

src/reference/asciidoc/xmpp.adoc

@@ -120,9 +120,6 @@ The samples above with the `namespace` manipulations can be simplified to someth
  payload-expression="#extension.bodies[0]"
  ----
 
-
-NOTE: The `extract-payload` option has been deprecated in favor of the new `payload-expression` one.
-
 [[xmpp-message-outbound-channel-adapter]]
 ==== Outbound Message Channel Adapter