From 84e7238922430380d5e0052e62fbc0ca1dd5462b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jes=C3=BAs=20Miguel=20Benito=20Calzada?= Date: Wed, 6 Nov 2024 10:28:12 +0100 Subject: [PATCH] Fix typo in overview-error-handling.adoc --- .../ROOT/pages/spring-cloud-stream/overview-error-handling.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/modules/ROOT/pages/spring-cloud-stream/overview-error-handling.adoc b/docs/modules/ROOT/pages/spring-cloud-stream/overview-error-handling.adoc index 94d6e6afc..f4870e5a4 100644 --- a/docs/modules/ROOT/pages/spring-cloud-stream/overview-error-handling.adoc +++ b/docs/modules/ROOT/pages/spring-cloud-stream/overview-error-handling.adoc @@ -47,7 +47,7 @@ While acceptable in some cases, for most cases, it is not, and we need some reco == Handle Error Messages In the previous section we mentioned that by default messages that resulted in error are effectively logged and dropped. The framework also exposes mechanism for you -to provide custom error handler (i.e., to send notification or write to database, etc). You can do so by adding `Consumer` that is specifically designed to accept `ErrorMessage` which aside form all the information about the error (e.g., stack trace etc) contains the original message (the one that triggered the error). +to provide custom error handler (i.e., to send notification or write to database, etc). You can do so by adding `Consumer` that is specifically designed to accept `ErrorMessage` which aside from all the information about the error (e.g., stack trace etc) contains the original message (the one that triggered the error). NOTE: Custom error handler is mutually exclusive with framework provided error handlers (i.e., logging and binder error handler - see previous section) to ensure that they do not interfere. [source,java]