INT-3835: Fix ERROR_CHANNEL Constant in Reference
JIRA: https://jira.spring.io/browse/INT-3835
This commit is contained in:
@@ -0,0 +1 @@
|
||||
source1
|
||||
@@ -160,7 +160,8 @@ Instead, to handle errors for asynchronous processes requires an asynchronous er
|
||||
Spring Integration supports error handling for its components by publishing errors to a Message Channel.
|
||||
Specifically, the Exception will become the payload of a Spring Integration Message.
|
||||
That Message will then be sent to a Message Channel that is resolved in a way that is similar to the 'replyChannel' resolution.
|
||||
First, if the request Message being handled at the time the Exception occurred contains an 'errorChannel' header (the header name is defined in the constant: IntegrationMessageHeaderAccessor.ERROR_CHANNEL), the ErrorMessage will be sent to that channel.
|
||||
First, if the request Message being handled at the time the Exception occurred contains an 'errorChannel' header (the
|
||||
header name is defined in the constant: MessageHeaders.ERROR_CHANNEL), the ErrorMessage will be sent to that channel.
|
||||
Otherwise, the error handler will send to a "global" channel whose bean name is "errorChannel" (this is also defined as a constant: IntegrationContextUtils.ERROR_CHANNEL_BEAN_NAME).
|
||||
|
||||
Whenever relying on Spring Integration's XML namespace support, a default "errorChannel" bean will be created behind the scenes.
|
||||
|
||||
Reference in New Issue
Block a user