remove ChannelResolver awareness from router parsers and FactoryBean
refactor 'channelIdentifierMap' -> 'channelMappings' and other clarity enhancements
trim array tokens
added AbstractMappingMessageRouter
This commit is part of Jira issue: INT-2186
Please see for reference: https://jira.springsource.org/browse/INT-2186
Several sub-issues are affected:
* INT-2137 - Add documentation for XPath Filter
* INT-2138 - Add documentation for XML Validating Filter
* INT-1917 - Document combination of SpEL and XPath expressions
* INT-2187 - Add documentation for xpath-header-enricher
* INT-1813:
polishing
INT-1813 added support for recognizig default components Added support for recognizing default components in parent ApplicationContext before they get auto-registered in child AC
Added support for recognizing default components in parent ApplicationContext before they get auto-registered in child AC
INT-1813 polishing
added containtBean check earlier, removed 'IfNecessary' from method names
Autostartup defaulted to false and isRunning() returned
the status of the associated connection factory instead
of its own status. Precluded it being started because
LifeCycle processor thought it was already started.
Previously, for single-use server sockets, and for client sockets
that have a collaborating inbound adapter, the socket timeout
was set to 10 seconds, with no way to set to infinity. The work
around was to set it to Integer.MAX_VALUE.
The intent was to avoid DoS attacks and mis-behaved clients, but
some users have expressed a desire to be able to set an infinite
timeout in both scenarios.
A future release may remove the 10 second default from the client
socket that has a collaborating inbound adapter, and default to
infinity. For this reason, that case now emits a warning.
The default 10 second timeout on single-use server sockets will
likely remain.
INT-1872 Remove WARN Log
We decided to eliminate the log message regarding a possible
future change to the default timeout for client sockets used
for request/reply.
Added a WARN log message to HttpRequestExecutingMessageHandler.
The warn message will let the user know that the 'extractPayload' attribute is meaningless if the provided 'httpMethod' will not send a request body.
